Connection timeout erases all unsaved changes

[atimholt]

Describe the bug

When attempting to save changes to your layout after a connection timeout, data loss occurs—the erasure of all changes made, while trying to save progress on those changes. That is, the hardware's current state overwrites the editor's state without warning or user permission.

To Reproduce
Steps to reproduce the behavior:

The error occurred for me after performing everyday multi-tasking (e.g. switching to my browser window, using Windows 11 task view), hearing a probably-relevant “usb device disconnected” sound, then attempting to save my changes. (I'm guessing it's pretty easy to manually induce a connection timeout error.)

To clarify: I didn't know that my connection had timed out until after beginning my attempt to save my progress. I had a vague suspicion, but wouldn't have even had that if I'd happened to have my sound muted.

Expected behavior
Because the vast majority of connection timeout errors occur without intent from the user, the program should continue seamlessly as if the timeout never occurred. I'd guess that the software is hard-coded to assume all (re)new(ed) connections made are the beginning of a new editing session, and that none of the previous editor contents are meaningful

Screenshots
(I did not know data loss would occur until after closing the “connection timeout error” dialog, so I didn't know to take a screenshot.)

chrysalis-debug.json.txt

Desktop (please complete the following information):

• OS: Windows 11
• Chrysalis Version: 0.13.3

Additional context
Hardware is a Model 100. Firmware version 0.92.1+94. I'll be updating it now.