That is because the driver and eswitch are in the tail. You couldn’t use that same UI on a mechanical switch light. So no, it couldn’t be applied to any type of light. It might with some but, most would require extensive modifications.
So you don’t believe in single mode lights? Sofirn C01 is one of my favorites.
I was indoctrinated to the quality light scene with the A6. It’s the one I like, so it’s in all my lights. Easy peasy.
Tally-ho
(Tally-ho)
44
Forward clicky and reverse clicky also have their own advantages and not all manufacturers will bother with the particular internal design required for a tail e-switch.
We understand your enthousiasm for the ramping UI and those who coded it will probably be flatted, but they would probably hate to see those who don’t need it or prefer something else, to be “forced” to use it if it would become a monopolistic/unique standard.
There are many people/manufacturers designing driver and UI and they know that not all people like or need the same thing, there is zero chance that they will definitely adopt zak’s personal preferences. Not mentionning that manufacturers will differentiate from others with their own UI.
Then in reality no, it will never happen, so no need for a ramping UI proselytism/evangelism/monomania/fixed idea.
You were joking/trolling, right ?
Kat
I can’t agree more! :+1: Particularly for any tactical use.
This has become a, make it my way and to hell with everyone else, thread.
You mean “my way or the highway”? Yeah, I tend to expect that from newcomers to any of the hobby forums I visit. Dunning-Kruger at its finest 
ZoomieFan
(ZoomieFan)
48
One doesn’t exclude the other.
Make a 100 mode UI.
Allow the user to set an output percentage* for each mode (including blinkies).
Allow the user to set the number of active modes.
Add option for ramping.
That way user-A can configure a two mode light with high and turbo, while another user can configure 5 moonlight modes and a blinkie.
*=A user configureble percentage. Not a hardcoded percentage.
Programmable modes creates its own headache. In particular for muggles and those who simply like simplicity.
I was playing with my new C8+ and accidentally entered programming mode by cycling through the levels a couple of times. I personally like options and even enjoy some level of complexity but I can see how this would annoy many. Or those you’re out with.
What about my single mode twisty? Silent for checking on the kids. Are we saying we want that to fall under a single ui?
manithree
(manithree)
50
FTFY
Just a few switch configurations (hardware UIs) I can think of just off the top of my head are:
Single Switch:
- Reverse clicky
- Forward clicky
- Selector ring
- “Other” ring (continuous, maybe)
- Slider
- Side e-switch
- Tail e-switch
- Twisty (I think there are multiple twisties - my ShiningBeam iMini worked like a twisty e-switch)
Multi-Switch
- Power + e-switch
- Multi e-switch
Just making all those work the same is virtually impossible, not to mention ludicrous. But, hey, I got confused once, so lets make them all illegal except the one I like.
I suggested that a looooong time ago. Leave N “slots” available. Be able to program each “slot” with a percentage (eg, 1-255). First 0 (ie, off) ends the list.
So 255/0/0/0/… is a 1-mode full-on light.
50/0/0/0/… would be a kiddie/muggle light, 1-mode, around 20% max.
255/80/20/0/… would be descending-order 3-mode light of around 100%/30%/8%.
And so on.
Maybe have “special” values 254/253/252 signify strobe/SOS/beacon.
Go crazy…
(Hownahell you’d program those values without a PhD, I have no idea.)
Now you’re getting into the spirit of things!
Maybe we should invest in matches…
I’ve had times when I couldn’t get them out of lock-out mode either. :person_facepalming:
Guys, this is just the tip of the iceberg.
We should standardize:
-All computing equipment UI across all platforms, including mobile.
-All TV and box platforms.
-All mobile device plans.
-All recipe ingredients and preparation methods.
-Political and religious views.
It’ll be great. More to come. I’ll be in charge.
Nah, tinderboxes are king.
Well, y’all know me… I depend on the little matches to light the large gas soaked torch.
I need the big torch!
To throw on the Bonfire! 
Lightning mode at first, changing to candlelight, and then an auto Sunset mode that turns off when it’s done.
elbakan1
(elbakan1)
58
My suggestion is one (1) mode.
One flashlight for every need.
With twenty five different lights,
you’re pretty much covered.
Cheers.
Scallywag
(Scallywag)
59
Minor correction, the driver is in the head still. But the tail switch is an e-switch, with the signal done through a second body tube. It's also worth noting, there is a mechanical tail-switch ramping firmware available, Crescendo by ToyKeeper.
As far as a standard UI for flashlights, no. That's ridiculous. Not everyone wants the same thing. Not all hardware even supports the same UI features. You're going to operate e-switches, reverse-clickies, forward-clickies, and dual-switches differently. Someone will make "+" and "-" mode buttons on their lights (wuben?). Someone will put three buttons! And then we'll have the magnetic-ring and other types of spin-something-to-adjust lights (nightcore, jetbeam).
The variety is good. We can all find things we like, or maybe we can at least find an interface we prefer and mod the UI...
Anyway, I fully support having your own collection wherein you maintain all the flashlights with the same UI. Probably NarsilM/Anduril... there's a few members around here who are nearly obsessively flashing their lights to one or the other. Or, hell, you could direct-wire your lights to physical switches and beat the FETs on output!
Just no next mode memory. Please.
travis
(travis)
60
Ridiculous.
one size does not fit all.
You want all automobiles to have the same engine, too?
