That's why I was amused by my own idea, and called it nonsense feature My use case was that, before discovering how "exit on shutter close" works, I used to open my cover (I have vertical camera cover, as opposed to horizontal vanilla one), to reveal LEDS only, without triggering camera or camera launch (which, with it's 6MB real RAM usage on idle, is unacceptable).

Of course it's all "void and null" for latest releases, so feel free to scratch it. Only one thing I would suggest doing, would be to "gray out" checkbox "close on camera cover", when "ignore camera cover state" is checked, to avoid confusion.

But user *must* be able to set ms values by hand, as duty cycle % in itself is meaningless and useless! Without possibility to set ms value, we would need to hardcode it - how long should it be, 1000 ms, 100 ms, or 2000 ms?

In duty cycle case, % of duty cycle is *calculation result* of ON ms : total ms ratio. So, natural thing is to have 2x input field for ms, and x% as calculated, non-imputable result.

If we decide to make % as imputable field, we, in fact, still allow at least one ms value input, just disguised as %, forcing user to pre-calculate real ms in mind (or calculator) to get any meaningful results.

/Estel