When pressing sequences of keys, it would be expected that the keyboard interface behaves exactly as the native Windows keyboard interface does. This means that slow and fast typists would recognize no change in the behavior of the keyboard interface when working inside a specific application. Even on multiple sequential key presses with overlap of keys, the interface should behave just like native windows. That would be the optimal case, I guess..
With JigsawWM I see some issues:
- one example is that when e.g. changing to
neovim application and trying to issue commands in command mode, the command mode is suddenly closed when trying to insert a standard Windows path containing a \ BACHSLASH character.
- another example is, when typing fast and thus sometimes holding two keys down simultaneously while typing a word. The keys don't get recognized in a reliably stable way. So, sometimes the
<SPACE> character is missing. Or other keys.
When pressing sequences of keys, it would be expected that the keyboard interface behaves exactly as the native Windows keyboard interface does. This means that slow and fast typists would recognize no change in the behavior of the keyboard interface when working inside a specific application. Even on multiple sequential key presses with overlap of keys, the interface should behave just like native windows. That would be the optimal case, I guess..
With
JigsawWMI see some issues:neovimapplication and trying to issue commands incommandmode, the command mode is suddenly closed when trying to insert a standard Windows path containing a\BACHSLASH character.<SPACE>character is missing. Or other keys.