tso: I think this is a "feature" of the app manager. If you download and install a deb, then try to overwrite it with a deb from the repos it notices that they have different sources. For some reason it doesn't just alert you and let you have the choice to continue. The easiest way past this is to uninstall your old version and install the new one from the repo.
This isn't a problem after the first install from the repo.
and now that we have a settings dialog, how silly of me would it be to ask for a user tunable light dialog? as in, a option to turn on something similar to the default light blacklight adjustment dialog, but with stepping sizes that can be set by the user?
I'd don't much see the advantage of limiting the selection (just tap generally in the area you want it, it'll be close enough, right?), but I don't see the harm in offering an option. I'll toss it on the TODO.
I'd don't much see the advantage of limiting the selection (just tap generally in the area you want it, it'll be close enough, right?), but I don't see the harm in offering an option. I'll toss it on the TODO.
It is actually very useful when using left/right keys, rather than tapping the screen. The problem is, of course, to find the most useful 3/4/5 values.
Is there a way to incorporate a defeat for the low light backlight brightness? A fancy way would be to add a third slider that sets the low light value. One could then set it 'anywhere' including equal brightness to the normal setting.
I don't understand the question. Is this related to the N810's light sensor?
This is a very useful app i listen to music alot so it is handy to adjust the volume, and when am done lower the brightness to keep the battery thanks alot for this app.
i am a green newbie desiring to learn coding for linux can anyone point me to the class one of linux to help me start , i have been searching but need some help thanks
One solution would be to modify just the hardware keys code to go to the nearest "hotspot" which could be like, every 15 or 20 brightness levels, instead of having the hardware keys move one at a time. What do you think of that? I don't like the idea of actually making set jumps much tho, as then we're right back in the same boat as the Nokia applet. >_<
Quick problem I have with this applet at the moment is that its popup window does not do urgent close like the "official" volume control applet (or many other applets, for that matter). This means that it stays open when I click on something other than it. In addition, it seems to be of the wrong window type, again compared to other such applets.
I don't understand the question. Is this related to the N810's light sensor?
Yes!. When the ambient light reduces to a certain level, the backlight does the same and this is a pain. (sorry for the poetry). I would like a way to defeat the low light function and thought that a third slider that controlled the backlight in its 'low' setting would allow for various situations including no dimming. ie: the hi and lo setting could be set equal and although the sensor sensed a low light condition and send the command to reduce the backlight brightness it reduced it to the same level as full brightness.
Don't know if you can get into that part of the code but though it worth asking.
Quick problem I have with this applet at the moment is that its popup window does not do urgent close like the "official" volume control applet (or many other applets, for that matter). This means that it stays open when I click on something other than it. In addition, it seems to be of the wrong window type, again compared to other such applets.
If you know how Nokia's applets manage to work like they do, then please let us know.
Yes!. When the ambient light reduces to a certain level, the backlight does the same and this is a pain. (sorry for the poetry). I would like a way to defeat the low light function and thought that a third slider that controlled the backlight in its 'low' setting would allow for various situations including no dimming. ie: the hi and lo setting could be set equal and although the sensor sensed a low light condition and send the command to reduce the backlight brightness it reduced it to the same level as full brightness.
It's on the TODO. The issue isn't really in our implementation (we have the light meter data, we have access to the backlight controls), but colliding with Nokia's implementation, as there doesn't seem to be a good way to turn it off or interface with it.
