OSDMenu Ideas/Features

[jediperry]

- Ability to pass a command and stay open (for adjustments, like hue, color, etc.) and receive more commands.


I second this feature request :).

[mattwire]

- Ability to have titles.
Will be available in next release
- Ability to have certain text bold/italic/etc.
This is quite complex to do since it requires a lot more variables/checking. However, I'll see what I can do.
- Ability to display girder string vars.
This is already possible (version 1.4) - see help.txt
- Ability to use bmps or transparent gif's as 'sub-menu' notices. (if there is a submenu use this arrow like picture or what not). (this could also be used for parent menus with a < instead of a >, etc.)
At the moment osdmenu doesn't know whether it is a submenu until it is executed. So this will require some thought...
- Ability to pass a command and stay open (for adjustments, like hue, color, etc.) and receive more commands.
Will be available in next release

[mattwire]

Here is an 'interim' release which adds the ability to pass a command and stay open. I think jediperry actually requested this feature before but I forgot to add it to my 'todo' list so it never got done!
I would have included it with the 1.4 release if I'd remembered since it's unbelievably simple to implement, just 3 lines of code.
osdmenu141.zip (http://homepage.ntlworld.com/graham.wire/osdmenu141.zip)
Please note that the 'official' release is still 1.40 but those of you who need this feature can use this version.

Usage:
as 1.4 - new variable:
closeonexecute=[0,1] - Specifies whether menu closes when command is executed or not - useful for adjustments menus (such as hue/saturation...).
When set to 0 close the menu by:
a)wait for timeout;
b)Goto submenu which has closeonexecute set to 1;
c)create a menuitem that executes a girder command to start the same menu - this will close it since it is already running.

[Necro]

I was working with OSDMenu and I had a few ideas that I thought would make it even better. Nothing too insanely hard I wouldnt think.

- Ability to have titles.
- Ability to have certain text bold/italic/etc.
- Ability to display girder string vars.
- Ability to use bmps or transparent gif's as 'sub-menu' notices. (if there is a submenu use this arrow like picture or what not). (this could also be used for parent menus with a < instead of a >, etc.)
- Ability to pass a command and stay open (for adjustments, like hue, color, etc.) and receive more commands.

Hope they made sense.

[Necro]

Damn Matt, talk about being on the ball :). The only other thing I could add (sorry I didnt mention this before) is an 'up and down' command. So if a menu item is selected, and you press 'up' it does one thing and 'down' it does another.

Sorry to be asking for so much. :)

[Necro]

I just thought of something else along these lines.

How about this...it's kind of drastic, but allows for an insane menuing system rather easily. Have OSDMenu have the ability to get a register from Girder, and USE THIS VALUE as where to start (the first menu). This would let you have one giant menu file, that interconnected all over the damn place - and have it all controlled very simply from girder.

So if you were in your tv program, you set OSDMENUITEM=TV. Use the OSDMenu plugin for 'mainmenu.ini' and it goes to the TV menu. WHich then has a 'back' option to take you to the 'main' menu for your system.

Just an idea...this (technically) can be done now, but it requires some intense girder register tampering. Or at least I think it does.