[PATCH v3 06/10] kdrive: add options to set default XKB properties

[Daniel Stone]

Hi,

On 4 December 2015 at 11:37, Laércio de Sousa
<laerciosousa at sme-mogidascruzes.sp.gov.br> wrote:
> 2015-04-05 3:22 GMT-03:00 Jeremy Huddleston Sequoia <jeremyhu at apple.com>:
>> While you're at it, would you mind updating Xephyr to support matching the
>> parent server's keyboard layout (similar to what Xnest does, cf:
>> 83fef4235db86343477b4ec9858c6ba35e1aa7d9)?  I never got around to doing
>> that.
>
>
> I'm investigating this right now. I have a working sample in my
> xf86-video-nested fork, using xcb-xkb, that I wanna try to port to Xephyr.
>
> Do you know if I can call XkbApplyMappingChange()+XkbDDXChangeControls()
> before InitKeyboardDeviceStruct()? For example, I would like to
> call XkbApplyMappingChange()+XkbDDXChangeControls() inside
> EphyrKeyboardInit(), which is called before InitKeyboardDeviceStruct() in
> kdrive/kinput.c.

No, you can't. But, for full bonus doing-it-properly points, you'd
want to get the XKB keymap in full (not the butchered core version)
from the host server, and then supply that directly at init time, via
an extra argument to InitKeyboardDeviceStruct(), or a new
InitKeyboardDeviceStructWithKeymap(), or something.

Cheers,
Daniel