Notices

Congo copernicus u just crossed the 1000 post mark !

hope to see a couple of more zeros

Hey, I've been spending most of my time this week on Orecchiette, but I did manage to get a few changes in on Lanterne. The main change in this update is the addition of buttons on the main screen to select between the white and red LEDs. (The red LED brightness is still controlled from the preferences panel, however.) Also, when "ignore camera cover" is set, all options on the preferences panel which utilize the camera cover should now be disabled.

I've been informed that the repository system is now once again accepting submissions, so I've submitted Lanterne 0.5.5 for the extras-devel repository. I've also updated the .deb file in the first post.

Thanks a lot! Controlling red led brightness from pref. panel is OK, and doesn't need changing, "methinks".

Control panel is looking great now, good job. When Lanterne is starting up with Stady On option enabled the default LED is the red one, is it possible to change that? I thought it was connected with that which one I had on, when closing the app (it would be nice feature), but that's not the case.

Strange, on my case, first run after update resulted in *white* LED being turned ON after startup. So, I changed it to red, closed application, and restarted. As expected, red LED came to live. I changed it to white, closed, and restarted - this time, counter-intuitively, it was still red LED to light up.

Maybe Copernicus coded it this way to bring non night-vision damaging led to live after startup? Still, it would be better to have it either run what was set before shutdown, or *cough cough* preferences option to set, what should be turned ON after startup (active only, if "turn on on startup" is active).

/Estel

Ack! Yeah, in the QSettings for this button, I used the red radio button's value "isEnabled()" rather than "isChecked()". Since it is always enabled, red is always coming up as the default. Thanks for the catch, I'll push up a fix asap...

Loving the new radio button
Works well.

Just an idea that came into my head: Is it possible to dim the screen while torch is in use?

Another idea: the camera button launches the camera application but only when the screen is on, when the screen is off (switched off with the side button) it doesnt.
Maybe it is possible to use the camera button when screen is off, camera cover open and lanterne is running?

(btw what application is used for selecting what happens when you open camera cover?)

Your screen will dim automatically after the timeout period.
It would be easy to lock the screen with a DBus call, but IDK if opening the application and then locking the screen would be annoying.
I suppose it would work ok if you had the auto-start option on.

Quite a lot of those things are possible with hacky workarounds I think Copernicus would like to avoid stuff like that. Things like that were tested in earlier versions and removed/commented out

Camera Lens Launcher
http://maemo.org/packages/view/cl-launcher/
With the current features of Lanterne the two applications work well.

So far, my experiments with using the N900 while the screen is off have been underwhelming; I just haven't been able to get the camera button to work the way I want it to. And, as Sixwheeledbeast notes, the camera button is already in heavy use by other apps (not the least being the camera app itself).

I suppose I could try to just lower the screen brightness while the app is running, but I'm not sure you can get the screen to be more dim than the red LED already is...