OSD on every command (like uIce)

[bazil749]

I'm real new to Girder as my post count will show....

I've tried the OSD plugin, but either it's not what I'm looking for or I don't know how to use it properly.

The problem:
I'm trying to set it up so that an OSD overly (nice lil' lime green text at the bottom of the screen) would pop up when I press a key for every command.

Sorry for comparing programs, but in uICE the button name is displayed by default if no event is associated, otherwise the event name is displayed.

Example: OSD displays "Start Winamp" when you push the key to start winamp.

Using OSD plugin:
right now the only way I can get this to work slightly is if I add all my commands as multigroups and add a second command to display the OSD using the plugin..

Also, the plugin clears the entire screen and displays the text in the middle of the screen. I haven't been able to get it display over the current monitor contents.



any help would be greatly appreciated.

Thank you.

[Promixis]

Yes, you must configure the osd for every command. For more extensive options, look at the XP OSD.

[Marsupial]

the way we do it with Girder, you configure what you want it to do. This way, some "commands" are not automatically displayed if you don't want to.

you must understand that Girder has "ANYTHING" as an input device... you wouldn't want to have an OSD for every program operations, every disk insertion or every single keypress on your keyboard or mouse movement...

all these are girder inputs. Therefore, its your job to determine what you want to happen...

have fun.

[bazil749]

True...

Thanks for the help.

[lmm]

I appreciate the flexibility, but the current Girder user interface for editing the .GML files is pretty awkward, because you have to think ahead of time whether you want a multigroup or a single command.

My preference would be to have the UI automatically set up a structure of

[set of commands]
[set of events which would cause those commands]

and make it really easy to just add an OSD to any existing event

Feature request for the next version :lol:

[Rob H]

It's not that difficult to turn a simple command into a multi group though!

All you have to do is create the Multigroup, drag the existing command into it and then drag any events for that command onto the multigroup. You should probably also give the multigroup a sensible name. At most that should take about 10 seconds per command.