Consider following use-case. You start typing the phrase "foo bar baz", but halfway you switch to some other task. You come back to your "foo bar b" and want to finish it with "az", but your keyboard layout is not what is used to be, and you get "foo bar bфя". At this point when I press the hotkey (double Shift) I'd expect only last two characters to be converted, when in practice you'll get the whole phrase converted to "ащщ ифк ифя".
Maybe it's just my habits and ways of working, but even while writing this issue it happened twice to me. I would edited something in the middle of the text, layout would be wrong, I'd press the hotkey and it would convert whole text starting from the line break.
What could help as well is a new mode, where app would detect a typing "session", that is a continuous uninterrupted sequence of the keystrokes, where interruptions are non-printable keypresses or mouse clicks.
Consider following use-case. You start typing the phrase "foo bar baz", but halfway you switch to some other task. You come back to your "foo bar b" and want to finish it with "az", but your keyboard layout is not what is used to be, and you get "foo bar bфя". At this point when I press the hotkey (double Shift) I'd expect only last two characters to be converted, when in practice you'll get the whole phrase converted to "ащщ ифк ифя".
Maybe it's just my habits and ways of working, but even while writing this issue it happened twice to me. I would edited something in the middle of the text, layout would be wrong, I'd press the hotkey and it would convert whole text starting from the line break.
What could help as well is a new mode, where app would detect a typing "session", that is a continuous uninterrupted sequence of the keystrokes, where interruptions are non-printable keypresses or mouse clicks.