The way it presents to the user is the if() set() not working and therefore all keyboard rules using it fail.
This bug is the result of keyboard options not being set correctly in keyman core integration with keyman for windows in version 15.
Describe the bug
First reported here
At the site are some test keyboards that can be used to verify. However, there is already an available test keyboard in the repo that can also be used. 021 - options.kmn
To Reproduce
- Load 021 - options.kmx
- Typed: a1a0a
Received: "no foo.no foo.no foo."
Expected: "no foo.foo.no foo"
Related issues
This may be also causing issue reported here
Windows 15.0.268
The way it presents to the user is the
if()set()not working and therefore all keyboard rules using it fail.This bug is the result of keyboard options not being set correctly in keyman core integration with keyman for windows in version 15.
Describe the bug
First reported here
At the site are some test keyboards that can be used to verify. However, there is already an available test keyboard in the repo that can also be used. 021 - options.kmn
To Reproduce
Received: "no foo.no foo.no foo."
Expected: "no foo.foo.no foo"
Related issues
This may be also causing issue reported here
Windows 15.0.268