Thanks, ToyKeeper, for such a great effort! The more I see this, the more “need” the FW3A in my hands :smiling_imp:
I know we will all enter in the field of personnal preference while answering your question, and maybe it is “dangerous” to answer it here on this thread, risking to “derail” it to the FW and not the FW3A
At the same time, it is appropriate to inform the people interested on this light about the FirmWare it will probably use!
Here is a link for your other thread/post where other discussions may appear about this: E-switch UI Development / FSM - #234 by ToyKeeper
My personal answer/preference to: “What sounds good to you?”
C and D !
Why C?
If we pass the C blink, we know the farthest regulated limit has been passed, so we may wanna go back a bit to enter the “regulated zone”, helping to save some battery even with it producing near 1000 lumens.
Why D?
Sometimes I see myself pressing the Emisar D4 switch trying to realize when it reaches the highest limit, when ramping up. If there wasn’t any “top blink” we might get “stuck” pressing the switch, because we don’t know if the highest limit has been reached or not. So, the “top” blink would be a nice indicator to let us move the finger away from the switch!
Why not A?
Obviously, as you said, the moonlight is easy to perceive when it is not getting lower!
Why not B?
If it will be regulated till the 1000 lumens, would it be necessary to have a previous blink to know the 1st regulated limit? Sure, it would help to save some more “juice” from the battery and produce less heat, but comparing to the D4 (as example), this one will have a wider regulated “space” so I don’t see a need for the B blink.
I don’t really mind the blinks as long as we don’t have “too much”
2 would be great to mark some important points, but at least 1 (the C) may be important to have it!
My perspective, only!
Thanks for your work again