Post #1820044

2026-04-23 16:25 UTC

I did a little polishing on my test tool, mostly adding a packet decoder and logger. Every event is 20 bytes long, with the last 12 always identical. Even though the first 8 bytes are different for each event I can decode what button was pressed or released from the first byte, not sure what the other 7 are for.

Replies (2)

@emorydunn@mastodon.tinycart.club 2026-04-23 16:30

The best part is I finally figured out how the official app is changing the mode of the dial so it stops sending keyboard events. I'd figured it was some setup packet when the app connects, but no. It's nothing so elegant. Every second the app sends a packet which tells the device to not do keyboard events. If the dial stops getting those packets it reverts to being a keyboard

Open ##1820045
@emorydunn@mastodon.tinycart.club 2026-04-27 02:45

Built a very basic button and jog wheel UI in very roughly the same configuration as the physical dial. Definitely calling this a win for Observation. Now I need to add actions for the button presses and dial events. Luckily I should be able to use some code from a previous physical input project to help with that #SwiftLang #SwiftUI

Open ##1820046