This is something that has nagged me for a while, but since I though it's not that important I never complained. When there's a submenu open the "Menu" key turns off the menu and the "Back" key goes back to the main menu. However if a plugin implements the osd as cOsdObject the same keys do the reverse: the "Menu" key goes back to the main menu and the "Back" key turns off the menu. Since conceptually (I mean, that's what the user sees on screen) the plugin osd is a submenu of the main menu (even if it isn't a cOsdMenu derivative) this difference in behaviour is confusing. At first I though I did something wrong in my plugins, but then I saw that other plugins do the same (unless their osd is derived from cOsdMenu) I looked at the menu code and it seems that's how things are supposed to work. Wouldn't it be possible to change that to make the same key do the same action regardless if the plugin uses cOsdObject or cOsdMenu?
Bye
Luca Olivetti wrote:
Basically its simple: The 'menu' key always opens the main menu, unless a menu is open. In that case, the menu is closed. This is even true for other VDR core dialogs that are not menu based, like channel info or audio.
On the other hand, I also tend to use the 'menu' key as 'close current OSD whatever' key, though it sometimes opens a menu I actually don't need.
Maybe this really would make a good usability change. It should be possible without serious regressions, since the 'menu' key is never passed to plugins anyway.
Cheers,
Udo
-
Luca Olivetti -
Nicolas Huillard -
Udo Richter