The Following 3 Users Say Thank You to qwazix For This Useful Post: | ||
![]() |
2013-06-13
, 01:35
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#152
|
The Following 4 Users Say Thank You to Copernicus For This Useful Post: | ||
![]() |
2013-06-13
, 02:31
|
|
Posts: 1,974 |
Thanked: 1,834 times |
Joined on Mar 2013
@ india
|
#153
|
The Following 2 Users Say Thank You to nokiabot For This Useful Post: | ||
![]() |
2013-06-13
, 09:11
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#154
|
Ah, well, that's kind of a conundrum; if you want to control the LEDs while the cover is closed, then really, the app should remain running while the cover is closed, right? I'm really not sure exactly how to both ignore the cover state and use the cover state at the same time. I could, for example, use the rule "If I'm ignoring the cover, but at some point the state goes from open to closed, I'll quit the app", it might work for your
I was envisaging a single slider like the volume control in status menu with % value next to it (or even across it) and Xms on - Yms off under it as calculated values.
Not only would it look cool but it would also allow for dynamic limiting of the duty cycle and/or longest on timer depending on the brightness (which I incidentally also envision as a slider).
But I will let Copernicus decide that
The Following 3 Users Say Thank You to Estel For This Useful Post: | ||
![]() |
2013-06-13
, 10:20
|
|
Posts: 6,453 |
Thanked: 20,983 times |
Joined on Sep 2012
@ UK
|
#155
|
But user *must* be able to set ms values by hand, as duty cycle % in itself is meaningless and useless
The Following 3 Users Say Thank You to pichlo For This Useful Post: | ||
![]() |
2013-06-13
, 10:58
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#156
|
Err, sorry, I wasn't very clear was I? I meant keep the period input as text but have the duty cycle controlled by a slider.
The Following 3 Users Say Thank You to Estel For This Useful Post: | ||
![]() |
2013-06-13
, 14:22
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#157
|
The Following 5 Users Say Thank You to Copernicus For This Useful Post: | ||
![]() |
2013-06-13
, 14:24
|
|
Posts: 1,986 |
Thanked: 7,698 times |
Joined on Dec 2010
@ Dayton, Ohio
|
#158
|
The Following 5 Users Say Thank You to Copernicus For This Useful Post: | ||
![]() |
2013-06-13
, 16:08
|
|
Posts: 5,028 |
Thanked: 8,613 times |
Joined on Mar 2011
|
#159
|
I suppose I could put something in, but would it really be useful? A light fixture with a light sensor works mainly because the light fixture is in a permanent location; you can be fairly certain that the light sensor is reacting to the light level in the room around you. But a cell phone is made to travel with you; this option would cause the LED to turn on every time you put it in your pocket...
The Following 6 Users Say Thank You to Estel For This Useful Post: | ||
![]() |
2013-06-13
, 17:36
|
|
Posts: 1,974 |
Thanked: 1,834 times |
Joined on Mar 2013
@ india
|
#160
|
I think he rather meant using this sensor to automatically disable torch, when sensor detects high ambient light, then, re-enabling it again, when in dark (only when torch is activated by user, not as general trigger).
While I can imagine some use-cases for it, I don't think it's worth the effort, still, even if it would be purely optional. Not to mention countless of situations, where user would forget to disable it (due to it going into OFF in lhigh ambient light), and indeed, torch would come back to life in pocket :P
/Estel
The Following User Says Thank You to nokiabot For This Useful Post: | ||
![]() |
Tags |
flashlight, lanterne, morse code, nokia n900, strobe light, torch |
|
Proud coding competition 2012 winner: ρcam
My other apps: speedcrunch N9 N900 Jolla –– contactlaunch –– timenow
Nemo UX blog: Grog
My website: qwazix.com
My job: oob