Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bug(windows): Keyboard configuration option does not change for active window. #5974

Open
rc-swag opened this issue Nov 26, 2021 · 1 comment

Comments

@rc-swag
Copy link
Contributor

rc-swag commented Nov 26, 2021

Describe the bug
With the IPA SIL Keyboard installed changing the option from "Before" to "After".
The change does not occur for the active app ie notepad. Opening a new app will take the new configuration. Or even closing and opening the same app.

This issue was identified when testing PR #5959 which addressed issue #5951
To Reproduce
This test requires IPA (SIL) keyboard to be installed
Step 1. Open notepad and check the behaviour of type "e>" or ">e". Depending on the current keyboard setting one of these options will give a "ɜ".
Step 2. Go to Keyman Configuration, select the IPA (SIL) keyboard, click on Keyboard options and choose Before. You may need to exit Keyman configuration before the default behaviour changes.
Step 3. Go back to Notepad, and observe that the "before" "after" change to configuration has not been applied.

Expected behavior
The configuration should have been applied to the current notepad instance.

Keyman for Windows:
Windows 10 x64, 15 alpha

Keyboard

  • Keyboard name: IPA (SIL)
@rc-swag rc-swag self-assigned this Nov 28, 2021
@mcdurdin mcdurdin modified the milestones: A15S18, A15S19 Nov 28, 2021
@mcdurdin mcdurdin modified the milestones: A15S19, A15S20 Dec 11, 2021
@mcdurdin mcdurdin modified the milestones: A15S20, A15S21, A15S22 Jan 3, 2022
@mcdurdin mcdurdin modified the milestones: A15S22, 15.0 Jan 23, 2022
@mcdurdin mcdurdin modified the milestones: 15.0, B15S6 Feb 23, 2022
@mcdurdin mcdurdin modified the milestones: B15S6, B15S5 Mar 27, 2022
@mcdurdin mcdurdin removed common/ core/ Keyman Core labels Mar 27, 2022
@mcdurdin mcdurdin modified the milestones: B15S6, B15S7 Apr 15, 2022
@mcdurdin mcdurdin modified the milestones: B15S7, A16S1 May 3, 2022
@mcdurdin mcdurdin modified the milestones: A16S1, A16S2 May 15, 2022
@mcdurdin mcdurdin modified the milestones: A16S2, A16S3 May 30, 2022
@mcdurdin mcdurdin modified the milestones: A16S3, A16S4 Jun 11, 2022
@mcdurdin mcdurdin modified the milestones: A16S4, A16S5 Jun 24, 2022
@mcdurdin mcdurdin modified the milestones: A16S5, A16S6 Jul 9, 2022
@mcdurdin mcdurdin modified the milestones: A16S6, A16S7 Jul 24, 2022
@mcdurdin mcdurdin modified the milestones: A16S7, A16S8 Aug 7, 2022
@mcdurdin mcdurdin modified the milestones: A16S8, A16S9 Aug 22, 2022
@mcdurdin mcdurdin modified the milestones: A16S9, A16S10 Sep 5, 2022
@rc-swag rc-swag modified the milestones: A16S10, A16S12 Sep 6, 2022
@rc-swag
Copy link
Contributor Author

rc-swag commented Oct 6, 2022

When the configuration changes there needs to be a call to the Keyman Engine to LoadOptionsCore. New apps get the options because LoadOptionsCore is called.

I need to investigate how TfrmKeyboardOptions.FireCommand results in the Windows Registry being updated and if there is anyway I can get the Keyman32 to call LoadOptionsCore at this point

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants