Attached a new version of my patch. You find two branches linked to this bug for maverick and natty. The patch sets SDL_DISABLE_LOCK_KEYS and get rid of the complete workaround in qemu-kvm. This requires SDL >= 1.2.14.
Stefan Weil wrote:
>The patch might fix part of the problem, but there remain more issues:
>
> * SDL also sends an SDL_KEYUP event for caps lock when the
> environment variable SDL_DISABLE_LOCK_KEYS is set.
> This mode is very useful but currently unsupported by qemu/kvm.
Addressed by new patch.
> * Num lock and caps lock are handled in a similar way by SDL.
> The patch only handles caps lock. Maybe this is less important
> because keyboard layouts which remap num lock are rare
> (I don't know any).
Addressed by new patch.
> * The keyboard status LEDs and the qemu client's keyboard status
> can become unsynchronized if the input focus changes from qemu
> to other applications.
Is this a regression of my patch or is it the case for the unpatched qemu too?
Attached a new version of my patch. You find two branches linked to this bug for maverick and natty. The patch sets SDL_DISABLE_ LOCK_KEYS and get rid of the complete workaround in qemu-kvm. This requires SDL >= 1.2.14.
Stefan Weil wrote: LOCK_KEYS is set.
>The patch might fix part of the problem, but there remain more issues:
>
> * SDL also sends an SDL_KEYUP event for caps lock when the
> environment variable SDL_DISABLE_
> This mode is very useful but currently unsupported by qemu/kvm.
Addressed by new patch.
> * Num lock and caps lock are handled in a similar way by SDL.
> The patch only handles caps lock. Maybe this is less important
> because keyboard layouts which remap num lock are rare
> (I don't know any).
Addressed by new patch.
> * The keyboard status LEDs and the qemu client's keyboard status
> can become unsynchronized if the input focus changes from qemu
> to other applications.
Is this a regression of my patch or is it the case for the unpatched qemu too?