View Single Post
Estel's Avatar
Posts: 5,028 | Thanked: 8,613 times | Joined on Mar 2011
#147
Originally Posted by pichlo View Post
Alternatively, replace the now superfluous "use indicator led as torch" checkbox with "allow using both LEDs simultaneously". I am thinking hard to come up with a situation when one would want to have both the white and the red LED on at the same time though.
I wonder, if it is even possible from hardware? I thought chip can drive *either* both white leds, or red one... But, in any case, difference between light levels are so extreme, that there would be 0 chance to even notice, that red led is ON, if white leds would be enabled (even at lowest, "torch" settings).

Originally Posted by Copernicus View Post
Question: do you have the "Ignore camera cover status" option checked? If so, Lanterne will ignore the camera cover. This includes not closing the app when the camera cover is closed...
Ough, my fault - of course I have it set. I wonder, couldn't Lanterne ignore camera cover state for purpose of turning LEDs off, but respect it for closing whole application at change from open to close (this and only this) state?

I know, it's funniest feature request I ever made, and I can certainly live without it, if it's too cumbersome to write (or basically, require wasting more than few minutes, to write such nonsense :P ).

Originally Posted by Copernicus View Post
Yes, and it was much more flexible as well. Dangerously flexible. The advantage of the "duty cycle" mechanism is that it shows you exactly where the danger is -- the higher the duty cycle, the greater the chance of damage to the LEDs. I'll look at providing other UI options, but I at least want to keep the duty cycle value somewhere, to let you know if you're in dangerous territory.
Originally Posted by pichlo View Post
How about keeping the duty cycle but providing a dynamic info line showing what it translates to in absolute terms.
Why not keeping more flexible ms - ms settings, and showing dynamically adjusted field with resulting duty cycle% (as non-imputable field, just a "calculated result", based on what we put into ms values)?

Originally Posted by Copernicus View Post
Ah, yeah, I've been trying to work out how best to do something like that. The big issue here is how to make it work in both landscape and portrait mode. The way I've got it now, Qt automagically resizes all the buttons for me; but splitting the buttons horizontally works better in landscape, and splitting them vertically works better in portrait. I'm still trying to find a way to customize landscape and portrait modes without being too cumbersome.

(...)

Actually, I'd prefer to have a generic White/Red switch somewhere, so that all the choices (Torch/Pulse/SOS/Morse) pick up the color switch once, rather than forcing each button to be split...
Hey, your idea with generic white/red switch is very good, it should be there instead of my proposed "indicator ON/OFF" button. As for landscape/portrait dillema, I would just split last button horizontally (ala landscape) - as said, even in portrait, they're going to be big enough for being comfortable. Other way around, it looks much worse.

/Estel
__________________
N900's aluminum backcover / body replacement
-
N900's HDMI-Out
-
Camera cover MOD
-
Measure battery's real capacity on-device
-
TrueCrypt 7.1 | ereswap | bnf
-
Hardware's mods research is costly. To support my work, please consider donating. Thank You!
 

The Following User Says Thank You to Estel For This Useful Post: