Thanks ToyKeeper (and the rest of the team) for your work on the FW3A. I’m really looking forward to seeing the finished torch, and then probably flashing Anduril onto everything that can run it.
I’d like to give a +1 to MascaratumB’s suggestion of blinks at point C and D, but I also have a question. When you reach reach either the minimum or maximum ramping level, does the light simply stop adjusting, or does it start ramping back in the other direction?
It stops. To ramp again, release the button and hold it again.
At the top end, it can sometimes be difficult to tell when it stopped. OTOH, it can also sometimes be difficult to see the blink at the top end, particularly when looking into the distance outside.
BC blinks. As you said, bottom and top of the ramp are pretty obvious anyway. But as long as they can be changed at compile time I’m good with anything.
I like the blink at moon because the Crescendo UI ramps down and up without stopping. and I like to know when I reach the bottom of the same reasons people like to know when the top is reached. Don’t like to press again to make sure.
ABCD blinks.
One thing I don’t like about ramping firmware is not knowing where I am, how much power is being used.
Blinks at these stages help greatly.
Personally I like the blinks at A and D. C would be helpful to know when you are leaving/entering full regulation. I don’t think b is really needed as you can just have it where you need/want it
If you are ramping up and hit the C point are people actually quick enough to stop it before it ramps over? I have a habit of redoing contact with the tail on the D4 to make sure it’s at a regulated level.
My preference is no blinks. Maybe a blink at D but definitely no mid-ramp blinks. Ramping UIs are much cooler when you can smoothly go from moonlight to max.
I think if there was a ‘shortcut’ to a known regulated level, ie 150lm, does that negate the need for blinks for some users?
Just my 2c though, naturally you should do whatever gets most votes.