thanks for the invert script feature! it seems to work well.
suggestion: the handy’s device name is The Handy – it would be cool turn on the ‘invert script’ checkbox automatically when this device is detected.
as for the ‘slow strokes not working’ issue, the handy specs claim it can consistently reproduce 32–400mm/s.
the problematic stroke i describe is 35mm/s which is close to the lower end of the range but works with wifi-based playback. fwiw, i assume this test script and video are made by @handyAlexander – i took it from his simple scripter. i wonder if he has any guesses about this. could it possibly be an issue with handy’s bluetooth playback feature? i’m on fw v3.2.3.
the device response feature does not seem to help. i tried values like [-20, -100, -200, -300, -500, -1000]ms, and it adversely affects overall performance. strokes finish faster or seem truncated, and very short strokes can just disappear which is bad. also, it does not fix the problem described above.
also, to be clear, it is not lag per se. it is just that slow strokes are not played back correctly.