On 12-12-12 22:30, Terje Andersen <teranders@gmail.com> wrote:
Den 06. des. 2012 17:35, skrev Alexander Wuerstlein:
Hello,
NX annoyingly adds hardcoded keybindings which overlap with e.g. GNOME's. Where in GNOME, Ctrl-Alt-t opens a new terminal, in NX and therefore in x2go, it closes the session.
Therefore I hacked together configurable keybinding support for nxagent/x2goagent as described here: http://wiki.x2go.org/doku.php/wiki:components:nxagent_keyboard_shortcuts
Currently this is experimental, so please test and report bugs, if there are no major breakages, you can expect it for version 3.5.0.17.
I took a look at that list and found that the meaning/function of several of the possible actions isn't clear to me (details below). Is it possible for someone knowledgeable to add a description for each of the actions, or point me, if possible, to a place with some more verbose information about those?
There is some documentation from nomachine, available at http://www.nomachine.com/ar/view.php?ar_id=AR03C00172 The actions in my patch are named from their context in the source code, but the relations to the descriptions on the nomachine page should mostly be clear. But generally, I didn't look up what the keystrokes do exactly, usually each keystroke sets some global variable which is then used somewhere in the code. My naming of the actions is therefore mostly based on the variable names, in the hopes of those being correct.
Also, is there any key combination which makes the X2Go client to catch/grab *all* keys, like <alt>+<tab> inside the session?
Doesn't the fullscreen mode do that? There is also some keygrab toggle, but that seems to be a debugging feature.
For me, these actions aren't clear:
- switch_all_screens
No idea here either :)
- defer
- ignore
I've introduced those ones, to be able to ignore Ctrl-Alt-Backspace or similar bindings like the unpatched nxagent does.
"special builds":
- force_synchronization
- debug_tree
- regions_on_screen
- test_input
- deactivate_input_devices
There is no documentation on those, anywhere, so one would have to read the code to come up with something. But since the actions are only available with special compile time flags anyways, most people will never be able to use them. I think its safe to just ignore those, I only included them for completeness, so that my code is really able to completely replace the old codepath.
Ciao,
Alexander Wuerstlein.