Not always sure what parts are new from the prior update, what with what I read back then, what has been discussed on Slack, and what WT has said in response to Treg questions - it becomes a jumble sometimes. But this part is interesting:
Jumps is one of TextBlade's defining capabilities, and it's made possible by a unique new combination of qualities:
Key feel superior to others, yet in a size that goes anywhere.
Once you use TextBlade, you quickly realize how integral the value of Jumps becomes.We've continued to expand our Test Release Group users, and they are giving Jumps a serious workout daily.
It turns out that Jumps is also a super effective way to shake out any quirky use cases.Jumps is sort of the extreme stress test for everything TextBlade can do, and every (sometimes crazy) thing we might want to do with a keyboard.
Jumps darts from one Bluetooth connection to another at very high speed, and frequently.It whisks you over from one host operating system to another.It gives you 6X more reasons to pair, and many good reasons to install diverse key maps.It recognizes gestures to know when you want to jump, and it even prompts TextBlade to translate keystrokes automatically, so you can use the same commands even when your host machines are quite different.
If there's any kind of latent issue in a nook or cranny, chances are Jumps will help find it.This past month we've been combing through the logs sent in by our TREG users, looking for hints of odd behavior when TextBlade is asked to do all these tasks in rapid succession, and across diverse machines and OS environments.
Most of our users are now reporting smooth performance across their different systems, but there's still a meaningful incidence of peculiar scenarios. We've gotten through many of these, and are checking off more each week.
We can't list all the little oddities we've fixed, but here's a few recent examples of where we're focused: 1. We found that in a few cases, all of the combined activity can occasionally put TextBlade into a ”La-La state” (credit to user Trace R.), where it gets confused and needs a reboot; and 2. We see some residual Bluetooth link interruptions in particular combos of OS's and sometimes other Bluetooth peripherals concurrently hooked up.
To diagnose the Bluetooth quirks, we've had to significantly amp up our test and monitoring firmware.We now have deep diagnostic logging capability right inside the Bluetooth core, inside the actual Bluetooth stack.This industrial strength monitoring capability had to be custom made by our Dev Team, and all the data is transported up to our App so users can easily send it to us to analyze.This is very powerful, and when any user gets a log of a particular state, we can pretty confidently knock it out.We'll be continuing to settle these kinds of points over the coming weeks, and see what users report after our updates.