A friend of mine asked me to explain the Gossamer user interface, thought I'd share the information with others...
The following schematic shows how the Gossamer/Acorn user interface works:
20 taps switches from one UI to the next. Since each UI has one bright mode, I just count the number of bright flashes instead of trying to keep track of the number of taps. 5 bright flashes means that I've made at least 20 taps. 40 taps (10 bright flashes by my count) switches from one power setting to the other.
And pretty much all user inputs start from the "off" position. Once you've "clicked", you really can't shift to the next option without clicking again - which is the "off" position. (If you're quick with your fingers, you could re-click the flashlight in less than one second and the Gossamer will process the sequence as a "tap" - but such manipulations aren't worth the bother, in my opinion.)
1dash1, this is a great chart. You know, I've meant to make something like this for a long time but never quite got around to doing so... thank you for taking the initiative!
:bow:
That said, it's not quite perfect. In the MemoryUI, you make no mention of the double-tap gesture that always puts the light at max output... it's a safety feature included so there is a reliable, predictable way to get max output no matter which level the light was in before. (This isn't an issue in the other user interfaces since they turn on at the same level every time, making the action needed to get to max easily predictable.)
It's also worth noting for newer users of the Acorn that a "tap" involves using the momentary capability on the tactical tailswitch to "blink" the light briefly... if you click the light on, then click it off, you'll most likely be too slow for the light to interpret your action as a tap. IMHO the "blink" terminology might be a little more descriptive, haven't really formed a firm opinion on that, to be honest.
As for the 20-tap and 40-tap gestures, it's well worth noting that one does not have to count those exactly... I designed the firmware to be very forgiving on the count, and so long as one does AT LEAST the specified number of taps, the intended action will take place. For example, 21 taps will advance to the next UI, as will 22, 25, or 29. Likewise, 40 taps will turn Miser on/off, as will 41 42, 44, 47, and 49 taps, among others. If one watches the light while tapping, he/she might not need to count at all! It's pretty clear by a change in sequence that the UI has changed, and clear by a sudden increase or decrease in all the levels that Miser has turned itself on or off.
It's also worth noting that the chart covers the "Califon" version of firmware. Other firmware revisions, though often fairly similar, will have more or fewer features. For example, the "Bailey" firmware does not have strobe or locator, nor does it incorporate the TheaterUI.
And pretty much all user inputs start from the "off" position. Once you've "clicked", you really can't shift to the next option without clicking again - which is the "off" position.
To be fair, this limitation has everything to do with the nature of the tailswitch itself. SureFire switches are TACTICAL in nature, meaning they allow for a momentary on but NOT a momentary off. That means there's no way for the Acorn to know you want to change to a different level unless you first turn off the flashlight. (Fenix and similar lights use a REVERSE tactical switch, which supports momentary OFF but not on... that's why they can change brightness without turning the light off... but they cannot be used for a momentary on, one must always click to turn the light on.)
(If you're quick with your fingers, you could re-click the flashlight in less than one second and the Gossamer will process the sequence as a "tap" - but such manipulations aren't worth the bother, in my opinion.)
Actually, it's 1/2 second, and in some custom versions of the firmware 1/4 second. Most mere mortals won't be able to click on then off quickly enough to finish within that timeframe. I know I can't!
oo: Besides which, one could always hold the momentary and click through to keep that particular level... that's actually very convenient!
Maybe you can work these into what otherwise is a fine chart. Thanks for doing this in the first place!
(Would you mind if I post the revised chart in my Eye Candy thread, and could you send me a copy of the chart in source form so I could perhaps revise it for other versions of the firmware? I will give you credit as originator of the chart.)