-
Notifications
You must be signed in to change notification settings - Fork 1
The converter misses repeating seqences #3
Description
Given my original XML, I still noticed a problem:
I was able to quickly write upper case letters with this map file without having to press caps-lock or doing long round trips, because I was mapping the upper case letters to a repeating movement of the lower case letters.
In my XML search for >S<. You will find this map:
<keyboardAction>
<keyboardActionType>INPUT_TEXT</keyboardActionType>
<movementSequence>INSIDE_CIRCLE;RIGHT;TOP;RIGHT;TOP;INSIDE_CIRCLE;</movementSequence>
<inputString>S</inputString>
<inputCapsLockString>s</inputCapsLockString>
</keyboardAction>For some reason this mapping is not available in the output, although the lower case mapping and roundtrip mappings will be:
<keyboardAction>
<keyboardActionType>INPUT_TEXT</keyboardActionType>
<movementSequence>INSIDE_CIRCLE;RIGHT;TOP;INSIDE_CIRCLE;</movementSequence>
<inputString>s</inputString>
<inputCapsLockString>S</inputCapsLockString>
</keyboardAction>
<keyboardAction>
<keyboardActionType>INPUT_TEXT</keyboardActionType>
<movementSequence>INSIDE_CIRCLE;RIGHT;TOP;LEFT;BOTTOM;RIGHT;TOP;INSIDE_CIRCLE;</movementSequence>
<inputString>S</inputString>
<inputCapsLockString>s</inputCapsLockString>
</keyboardAction>This will be converted to the output.
I think this is due to the fact that these letters are part of default sectors that will be mapped without custom definitions. But in doing so, you would need to check if the origin follows the default behavior, which is not very trivial.
I think a simple work-around would be to have a flag that allows me to enforce to add all letters as hidden mappings as well, then I could simply remove the redundant entries, but keep my upper-case shortcuts.