2 ms·

Thanks for letting me know. I've actually been pushing a couple updates today to try to address this and figure out the right pressure or hold-time threshold be

Thanks for letting me know. I've actually been pushing a couple updates today to try to address this and figure out the right pressure or hold-time threshold before the slider activates. It's a tricky balance, but I just increased it to .85 or 300 ms, and hopefully that's a little better. I know that the mobile experience has some issues, but I'll try out some other solutions this week. For now, if you accidentally marq a marqt when scrolling, you can set your marq back to neutral by sliding it somewhere near the middle of the marqt. It sort of acts like an undo.

arthurhur 3y ago
Okay, I think I have a decent working solution for the scrolling actions accidentally triggering the switches. Basically, if the action is more of a quick vertical swipe, it resets the switch to the previous state (so if delta of y > delta of x, then undo, unless the user has been dragging for over 1500 ms). Hopefully this solves the mistaken swiping issue. For context, it took me a couple different approaches to get it right, mostly because it seems like iOS doesn't support a lot of the Touch API capabilities in browsers like force, etc. Also, if you're on Android, I added a tiny vibrate as you tick up or down your marq – I haven't been able to test it out, but if you're on an Android, please let me know if a) it's working, and b) if the vibrate length feels right (10 ms), and I will adjust as needed. Thank you!