Switching keyboard layouts causes issues with . (text entry) functionality

[jboolean]

I frequently switch between QWERTY and Dvorak keyboard layouts. If I launch QS in one layout and switch to another while it's running, the trigger for text entry (what should be the period key) gets stuck on whatever physical key used to be the period when I launched the program.

If launched in QWERTY then switched to Dvorak
Attempting to type an 'e' starts the text entry field. Typing a period just types a period like any other character.

If launched in Dvorak then switched to QWERTY
Attempting to type a 'v' starts the text entry field. Typing a period just types a period like any other character.

[skurfer]

Did this just start with the release of B70, or has it always ben like that?

[jboolean]

No, I had b69 when I wrote this. I don't remember if it was associated with any specific update.

[skurfer]

Well then I'll ask the opposite: Does it still happen with B70? A new preference was added that allows you to always use a specific layout within Quicksilver (regardless of the active layout for the rest of the system). I'm wondering if a possible side effect of the new code is that it'll be better at picking up the current layout after a relaunch.

[jboolean]

If that option is turned off, the problems still occurs. If it's turned on,
then it works fine regardless of the layout it was launched in.

On Sun, Sep 23, 2012 at 11:50 AM, Rob McBroom notifications@github.comwrote:

Well then I'll ask the opposite: Does it still happen with B70? A new
preference was added that allows you to always use a specific layout within
Quicksilver (regardless of the active layout for the rest of the system).
I'm wondering if a possible side effect of the new code is that it'll be
better at picking up the current layout after a relaunch.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1134#issuecomment-8799614.

[pjrobertson]

I think this is a known limitation with NDKeyboardLayout.

@tiennou mentioned it here:

#942 (comment)

That is - we need to register for the correct notif for when the keyboard
layout changed.
Perhaps @tiennou could make a pull request to the NDKeyboardLayout repo…?
;-)

On 23 September 2012 16:58, jboolean notifications@github.com wrote:

If that option is turned off, the problems still occurs. If it's turned
on,
then it works fine regardless of the layout it was launched in.
-----Julian

On Sun, Sep 23, 2012 at 11:50 AM, Rob McBroom notifications@github.comwrote:

Well then I'll ask the opposite: Does it still happen with B70? A new
preference was added that allows you to always use a specific layout
within
Quicksilver (regardless of the active layout for the rest of the
system).
I'm wondering if a possible side effect of the new code is that it'll be
better at picking up the current layout after a relaunch.

—
Reply to this email directly or view it on GitHub<
https://github.com/quicksilver/Quicksilver/issues/1134#issuecomment-8799614>.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1134#issuecomment-8799708.

[tiennou]

I will. I'm also considering adding that as a git module, and I thought that forking it under the quicksilver account would allow us to keep it closer to us ;-) ?

[skurfer]

Yeah, I thought about doing the same for LaunchAtLoginController. Fork it to the quicksilver organization, fix it, submit a pull request, then add our fork as a submodule so we could start using the fixed version immediately. We decided not to in that case, but it's still a good trick.

[timvisher]

This problem surfaced me when I transitioned from Snow Leopard to Mountain Lion. I never installed Lion so I don't know if the problem was present there.