Bug#395257: This bug was reproducible with the NEWT frontend too

[Attilio Fiandrotti <attilio.fiandrotti@gmail.com>]

Frans Pop wrote:
> On Thursday 02 November 2006 07:10, Christian Perrier wrote:
>
> > Why do you expect that changing the language will change the keyboard
> > layout?
>
>
> Heh, stupid of me. I missed that when reading these earlier :-P
> Of course, you have to go back to keyboard selection to change the 
> keyboard. And I've often enough seen that this works for the newt 
> frontend (and just verified that it still does).
>
> It also works for g-i, but _only_ for VT2, not for VT5!
> The first selection works on VT5, subsequent selections in kbd-chooser do 
> nothing.

Ok, now i got it too (i tought changing language would have changed 
keymap too).

Yesterday i went further, and associating the call

dfb_input_device_reload_keymap( dfb_input_device_at( DIDID_KEYBOARD ) );

to the Insert key in the df_input application.
I could verify the keymap reloading worked correctly at DirectFB level 
when i issued, in sequence, various "loadkeys it" and "loadkeys us" from 
a different VT.

Then, i took a simple GTK app with a text widget where to input text and 
a button to force keymap reloading, and still i could switch from us to 
it and back to us again issuing "loadkeys .." from another VT and then 
forcing keymap reloading.

I wonder how keymap switching is implemented in the d-i : isn't 
"loadkeys xxx" called every time the user wants to change keymap, like 
on a regular debian system ?

cheers

Attilio