GNOME Bugzilla – Bug 589856
Add key for displaying controls
Last modified: 2013-02-22 12:18:04 UTC
Sometimes it's useful to be able to briefly display the controls in full screen mode by pressing a key, instead of moving the mouse. As discussed in bug #559024 (http://bugzilla.gnome.org/show_bug.cgi?id=559024#c10), this is a separate bug report for this.
Created attachment 139273 [details] [review] display-controls.patch Make it possible to briefly display the controls in full screen mode by pressing D, using the command-line argument --display-controls or a LIRC key. It's not tested yet and I'm not sure about the LIRC stuff.
KEY_DISPLAY is definitely wrong for the LIRC config. Could you please use "--show-controls" instead of "--display-controls" as well? Rest looks fine.
Created attachment 139679 [details] [review] display-controls-2.patch Ok, changed it to "show" everywhere. Should we change the key to "s" or "c" as well? I commented out the LIRC configuration as with another command, the user can choose a key herself.
I just checked the driver for the PS3 Bluetooth remote, and you should use KEY_INFO for showing the controls (and the LIRC bits should actually toggle the controls showing, not just show them). There's also a "toggle-controls" which is only used for windowed mode, so "show-controls" should work in windowed mode as well.
(In reply to comment #4) > (and the LIRC bits should actually toggle the > controls showing, not just show them). Should there be a "toggle controls" for full-screen mode, which will always show the controls? > There's also a "toggle-controls" which is only used for windowed mode, so > "show-controls" should work in windowed mode as well. Should it behave as if "toggle controls" was pressed, then wait a time and then toggle them again? Or should it show just the controls (without the menu or sidebar)?
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 694435 ***