I have done some rather extensive testing with double press, but for boost mode, not previous mode. It was brought to my attention in a thread I made asking for these kind of things: Driver giveaway: Constant current 17mm drivers, winners (finally) announced, post #2. (double tap discussion started at post #123).
So I have to disagree a little. I noticed with double press on a clicky that you can go wrong. There is a timing issue that must be dealt with, and that is you have to have a time difference between double press and two single presses. If I want to go up two modes I need to do two single presses. If I do them too fast they are interpreted as a double press. Too me this timing distinction faces the exact same issues as short press vs long press. I implemented it and settled on 200ms time limit for double press.
Believe me, I have tested this stuff a lot. I don’t get short press vs long press wrong. If the time limits are set fine, and you have hardware to support exact timing (like OTSM), messing up short press and long press is as difficult for me as it is for you to mess up double press vs two single presses. With that said, I now have support for double press so I’ll have a look at making a UI that uses it for previous mode. I have the space for it.
It’s this super-customisable UI: Sterownik driver LED 4,2/2,8A programowalny extended v3.5 HE - www.swiatelka.pl
Also the one Mocarny is talking about. The google chrome translation is very good.
Interesting, thanks for posting. I’ll have a closer look at that, might give me some suggestions.
Anyhow, this is a Convoy thread, I should stop hijacking it.