@colinng The things you are talking about (essentially performance issues) are quite important. I do a LOT of troubleshooting for people on their computers and learned a very valuable lesson one day back when the “Intel Pentium” was first released. I forget now what it was precisely (windows installation?), but some aspect of a brand new computer build and setup was taking EONS to complete. I’d get to the same spot, wait five or six minutes, see nothing at all (also noticing it was non responsive to input), turn the machine off, reseat the memory, cpu, cards, etc, and try again, to no avail.
Turns out the (then brand new) Pentium BIOS was slowing things down so much at install time that it took something like TEN MINUTES to get past a screen that normally took a few seconds on my trusty 486! This was just a simple growing pain - the 386/486 BIOSes were so mature at that time, and Pentium so new, that I’d come to expect something that just wasn’t the case on the newer system. This, coupled with my expectation that “everything would be faster” on the new shiny - the Pentium computer, and it wasn’t until I eventually was reading the flimsy motherboard/BIOS manual long enough while on that screen that it eventually got past it... after close to TEN MINUTES. Only then did I know if I’d just been patient it would all have been fine.
This is of course an extreme example, but still, it is important that new users have an experience as close to (or better than) their expectations as possible.
I’m glad to hear there is some apparent buffering present in the keyboard when doing a jump. The chording is more intriguing. Are you saying if you try a chord before the TextBlade is fully powered up that you can no longer chord afterwards? Or perhaps it was that way originally and then they had to fix that?