> On Wed, Nov 13, 2002 at 12:02:51AM +0100, M. Gerards wrote:
> > I only support the compiled format. When a user wants to use the XKB format
> the
> > external xkbcomp program can be used to compile the keymap. This action
> data
> > structure can't be modified without losing compatibility.
>
> T
On Wed, Nov 13, 2002 at 12:22:07AM +0100, Marcus Brinkmann wrote:
> On Wed, Nov 13, 2002 at 12:02:51AM +0100, M. Gerards wrote:
> > I only support the compiled format. When a user wants to use the XKB format the
> > external xkbcomp program can be used to compile the keymap. This action data
> > st
On Wed, Nov 13, 2002 at 12:02:51AM +0100, M. Gerards wrote:
> I only support the compiled format. When a user wants to use the XKB format the
> external xkbcomp program can be used to compile the keymap. This action data
> structure can't be modified without losing compatibility.
There is no gain
Quoting Marcus Brinkmann <[EMAIL PROTECTED]>:
> On Mon, Nov 11, 2002 at 02:49:33PM +0100, M. Gerards wrote:
> > The first problem is the scancode to keycod translation. At the moment I've
>
> > hardcoded this translation (XKB also works like this.). I'm not happy with
> this
> > because this wil
On Mon, Nov 11, 2002 at 02:49:33PM +0100, M. Gerards wrote:
> The first problem is the scancode to keycod translation. At the moment I've
> hardcoded this translation (XKB also works like this.). I'm not happy with this
> because this will cause problems for exotic keyboards. I'm thinking abut a