when mistakes are made, excessive backspace is often required

[evgenyfadeev]

That is - when I practice and enter a word incorrectly I often find needing to type backspace way more than the number of strokes necessary to erase the word I've mistyped.

Sometimes the input that appears even seemingly from a previous exercise.

Is that an issue with the react state in this app or a feature of plover?

[didoesdigital]

@evgenyfadeev I'm not sure I understand exactly what you're seeing. Can you please share an example of this? Perhaps a description of specific words or a video. And can you confirm if you mean you've typed an actual "backspace" or if you mean the steno "undo stroke" functionality (which is usually the * star key)?

My best guess is that you've pressed keys that would result in a multi-stroke word. For example, if you had the material "sigh" followed by "lend" and wrote SAOEU then misstroked HREPBT instead of HREPBD, Plover would see that as SAOEU/HREPBT and try to back track to the previous word to re-write it like changing "sigh" to "silent". Typey Type would have already marked the first word "sigh" as correct and deleted it so you would only get "lent". Then pressing * to undo the HREPBT stroke would leave you with some weird text like "gh" from the end of "sigh".

[evgenyfadeev]

@didoesdigital yes - when I type multistroke words and make a mistake, after a while typing * repeatedly would bring out more and more of the previously typed input (normally I would not expect that, because the previous word was entered correctly and was accepted). I see sometimes the same behaviour in the Plovel lookup tool as well, that's why I suspect it might be a feature of the Plover software.

I'll try to record a screencast and share it somehow.

Thanks.

[evgenyfadeev]

@didoesdigital here are a few short snipppets where after making a mistake I could see the previously correctly entered words back in the input by hitting * I would assume that there should be no way to return to the previously accepted words by hitting *, but it happens after making a mistake (possibly this is exclusive to multisyllable words).

Here is a decent example - after a mistake in the final word in this clip I was able to "backpedal" 3 or 4 words backwards by hitting *:

https://jam.dev/c/95442494-6af8-477d-9e66-f0f9e489f2f8

More examples below - although with less of a dramatic effect:

https://jam.dev/c/4387de90-fb7e-43c2-a538-8255ff37535b

https://jam.dev/c/1bc5ac54-8f61-4669-bcf8-0002a99eb2ac

https://jam.dev/c/6c58231d-4781-48f1-bd27-c54f1b8706b8

I'll update this ticket if I find a better example.