xpra icon
Bug tracker and wiki

Opened 6 years ago

Last modified 5 years ago

#134 accepted enhancement

allow user to specify key mapping overrides

Reported by: Antoine Martin Owned by: Antoine Martin
Priority: minor Milestone: future
Component: client Version: 0.3.x
Keywords: Cc:

Description (last modified by Antoine Martin)

On some platforms (particularly OSX), it seems that the gtk code does not detect the key mappings correctly - or that users want to use different key mappings with it, so the only way to do the right thing is to explicitly tell xpra about the desired mappings.

For example (taken from this mailing list post)
"Make esc and alt behave as Meta":

clear Mod1
clear Mod2
keycode 63 = Mode_switch
keycode 66 = Meta_L
keycode 69 = Meta_R
add Mod1 = Meta_L Meta_R
add Mod2 = Mode_switch

Maybe something like:

xpra
    --keycode="66 = Meta_L"
    --modifier="Mod1 = Meta_L Meta_R"
    ...

Or even:

xpra
    --keycode-file="path/to/xmodmap-pke-file"
    --modifier-file="path/to/xmodmap-pm-file"
    ...

We then need to keep hold of those values, and use them to override the keyboard detection code (which may fire again after startup).

Change History (3)

comment:1 Changed 6 years ago by Antoine Martin

Description: modified (diff)
Status: newaccepted

comment:2 Changed 6 years ago by Antoine Martin

Talking about OSX specifically, there used to be some code in versions 0.0.7.3x that explicitly mapped meta to alt for OSX:

    def grok_modifier_map(self, display_source):
        map = ClientExtrasBase.grok_modifier_map(self, display_source)
        map["meta"] = 1 << 3
        return  map

Maybe this is all we need to do. The difficulty here is that the client no longer sends any modifier map: self._client_extras.get_keymap_modifiers() returns empty values for osx and lets the server decide.

comment:3 Changed 5 years ago by Antoine Martin

Milestone: 0.4future

Probably less important now that the keyboard support is improved - delaying.

Note: See TracTickets for help on using tickets.