Gemini PR protocol can become out of sync

[morinted]

Summary

Sometimes, while @stenoknight is writing on her new Gemini PR machine, it starts producing inaccurate strokes, as if the number bar were hit. I'm guessing this is because the steno somehow gets offset and maybe S- becomes #, T- becomes S-, etc. I asked her to record more detail if it ever happens when she's not on a realtime job.

Reproducing

The bug is intermittent, but happens with a newer machine over Bluetooth. She says there's a difference between the Plover versions:

• Plover 3 actually stops all output, and the reconnect button must be hit to start using the machine again.
• Plover 4 keeps going, but gets the wrong steno output.

I think this behavior is expected if you consider this change

Perhaps a fix would be reintroducing the removed code in a state that doesn't produce an exception.

Plover Version

• Latest weekly
• Plover 3.1.1

System

Mirabai is running an Infinity Ergonomic Gen O on a Windows computer with the Toshiba Bluetooth stack.