A "drag handle"? I was planning on trying to add light-meter support this release, but I'm still not exactly sure *how* it will handle the light-sensor, exactly. What do you mean by "drag handle"?
Also, anyone else who wants to suggest ways to interface with the light sensor, please do! I don't have an n810 myself, so I haven't thought about it much before now...
Well, I've noticed that the default light sensor control seems to still run with this applet, until you adjust the light level from the applet which seems to override the built in setting. Then if you put it back in the dark, the screen dims (from the light, not from inactivity). Bringing it back into the light brightens the screen, but not to this applet's setting. I just confirmed this by turning the brightness all the way up (screen brightened), then putting it under my desk but still moving around the control panel (screen dimmed), then bringing it out into the light again (screen brightened), and then turning the brightness down by an eighth on this applet (screen brightened, rather than dimming).
I don't know how you would interface to override this default behavior (haven't looked into it myself either, might be an option over dbus). But, I do have an idea of how I'd like to control it. Unfortunately, by idea may get back to the issue of having the applet do to much, and it may just be way more detail than any one else really wants. I'd like to be able to set the equation for brightness for different segments of light level. That is, I'd like to be able to say "if lux < 50, then b = lux / 150 + 3, if lux < 150 & > 50 then b = lux / 100 + 15,..."
It's just an idea. Like I said, I don't know if it would be more work than should be done, or if any one else would use it.
Slightly related is this feature request. For anybody who has an issue with this, moreDimmingOptions is a decent stop-gap until a more elegant solution can be reached (which will involve changes to a Nokia "entity" or two, so don't hold your breath :\).
Unfortunately, that isn't how it works. The popdown-window event only happens WHEN the window is closing, which happens when my code tells it to hide the window, and my code doesn't know to hide the window unless it gets the right signal, which it doesn't in certain cases.
I could be wrong, but I tried this before and I just tried several variations on this again... If you think you can make it work, the code is in SVN or downloadable in the files section on the garage, and *please* submit a patch!
I have submitted a patch against version 0.9-2 in your garage tracker. The popdown signal actually does work the way I suggested it would, but you were only setting a flag in it. My patch is a single line that closes the window when it receives any sort of outside click.
Okay, I didn't test my patch enough. rm_you, you are correct in your understanding of the popdown event. My testing involved clicking on the home screen as my "away tap" which works with your version as well. Colour me embarassed! I will let you know if I have any more "bright ideas"
As an update to my previous post #125, I did a reinstall (doh!) and just to try it -- since at this point I had nothing to lose, I installed the update... works fine now. Who knows.
0.9b in diablo works well. I like the hardware keys, and I like the dinging for the sound. However, n810 also supports 0 backlight, perhaps have the dialog read "n8x0 users beware!"
