This commit disables the "ToggleFullScreen" mapping in standalone mode (only) without the need to hack the actual keymap files.
changed: ability to ignore and skip specifiy key mappings when runnin…
…g in standalone mode
Any thoughts on overriding this in the case debug is enabled from GUI settings?
No thoughts about it really. Mind explaining why it should be disabled in case of debug enabled?
Shouldn't ToggleFullScreen be better blocked in graphics context when running standalone?
@FernetMenta blocking is a really bad idea as some external players want fullscreen and suspend XBMC. Same applies to various launcher addons (emulator and the likes).
We have just discussed this in the Linux forum. Running XBMC standalone needs special handling for X windows, setting the override redirect flag. Not doing so results in poor rendering performance. That means you can't launch other gui application when running XBMC standalone. For those cases you need a window manager.
@FernetMenta but running --standalone is possible with a window manager as well. Blocking the toggle would cause some serious issues for all the addons on XBMCbuntu and derivates i'd guess.
It currently checks for standalone in order to determine if override redirect flag should be set. A different approach would be checking for a window manager: FernetMenta@b1369f4
Some users do weird things, e.g. launching a window manager in a script to bring up a browser. If no WM is present, no other gui applications should be launched nor XBMC minimized or windowed.
I'll leave that to you guys ,) I just want to avoid silly toggles that end up in a user nightmare.
Make PIN input secret