MP3Car.com - View Single Post - Autodimming monitor after 2 seconds of inactivity. (Solution inside)

RPM_VR4 · 01-21-2006, 07:31 PM

You are crazy on top of things JIT

That's a pretty cool hack too Tipastar.

There are too many damn hacks in this community though (still it is cool that it can currently be done). It is way too hard to get everything setup correctly on a new machine. We need a background program (like GC) or front-end plug-in. Maybe the entire program would be a screen-saver with a details page that lets you set the settings. Or maybe in addition to the program/plug-in you would have to enable a screen-saver that notifies the process of a screen-saver event (this screen-saver could by auto-installed/selected by the app/plugin of course).

Here is the full feature set as I see it...

Code:

First, you could use a light sensor if you have one.
If not, it could fine out sun-rise/set times like GC.
You set the max fade-out for night time.
For the hour leading up to night time, it would fade only partially.
If you had a light sensor, it would fade based on its level.
You set the screen-saver activity time-out
You set the amount of time it takes to fade to full dark.
You set the time to fade back up after a touch.

Preferably if it were non-screen-saver based, you could also set the max-unfaded brightness in case you never want it full-bright at night, even when you are using it.

Code:

Example:
I would set max fade-out level to 70% brightness (I don't like much of a dim).
I would set night non-fade-out to 90% brightness.
I would have it start to fade out after 3 seconds of inactivity.
I would have it take an additional 5 seconds to reach full fade-out.
On touch, I would have it quickly fade back up over 0.5 seconds.

Now, from my example, if it is totally dark at 8:00pm, and the current time is 7:30pm, the display would be at 95% brightness when in use, and fade to 85% brightness when not in use (because 7:30 is the half-way point between 7-8). Once it is 8, it would be 90% when used and 70% when idle just as I set it to.

This way there would be a nice time-fade that would eliminate the chance of having it suddenly fading-out if you are driving at 8:00. I like features like this to not even be noticeable.

Of course, an analog light sensor that could report 5 or more levels between full light and full darkness would be even better.

01-21-2006, 07:31 PM	#14
RPM_VR4 Banned Join Date: Nov 2004 Location: L.A. Posts: 1,944	You are crazy on top of things JIT That's a pretty cool hack too Tipastar. There are too many damn hacks in this community though (still it is cool that it can currently be done). It is way too hard to get everything setup correctly on a new machine. We need a background program (like GC) or front-end plug-in. Maybe the entire program would be a screen-saver with a details page that lets you set the settings. Or maybe in addition to the program/plug-in you would have to enable a screen-saver that notifies the process of a screen-saver event (this screen-saver could by auto-installed/selected by the app/plugin of course). Here is the full feature set as I see it... Code: First, you could use a light sensor if you have one. If not, it could fine out sun-rise/set times like GC. You set the max fade-out for night time. For the hour leading up to night time, it would fade only partially. If you had a light sensor, it would fade based on its level. You set the screen-saver activity time-out You set the amount of time it takes to fade to full dark. You set the time to fade back up after a touch. Preferably if it were non-screen-saver based, you could also set the max-unfaded brightness in case you never want it full-bright at night, even when you are using it. Code: Example: I would set max fade-out level to 70% brightness (I don't like much of a dim). I would set night non-fade-out to 90% brightness. I would have it start to fade out after 3 seconds of inactivity. I would have it take an additional 5 seconds to reach full fade-out. On touch, I would have it quickly fade back up over 0.5 seconds. Now, from my example, if it is totally dark at 8:00pm, and the current time is 7:30pm, the display would be at 95% brightness when in use, and fade to 85% brightness when not in use (because 7:30 is the half-way point between 7-8). Once it is 8, it would be 90% when used and 70% when idle just as I set it to. This way there would be a nice time-fade that would eliminate the chance of having it suddenly fading-out if you are driving at 8:00. I like features like this to not even be noticeable. Of course, an analog light sensor that could report 5 or more levels between full light and full darkness would be even better.