didnt means seconds, meant minutes. it was actually the clock that made me point out modules stopping working while i was watching a movie on other screen as i noticed wrong time

Yeah, but that has already been fixed in v18.1.

i know, my point is that the clock is one of the things that shouldnt go below once a minute (opposed to some things that can stop completely)

Goes without saying... and how about an opinion on the above?

maybe grey for off, green+ white for medium, green+orange for max?

Well, only the button itself changes color, the leaf remains white.

So gray button for off, green button for medium, orange button for max? Why orange and not red?

In the mean time here is what I have so far:

Medium Power Saving Mode:

1. All cosmetic animations are disabled. This means:

a) Wanda stops swimming.
b) Rotating globe style of the Email Checker module stops rotating even if there is mail.
c) Smooth gauge needle animations are disabled (i.e.; needle jumps from value to value)
d) User Interface slide animations are disabled.
e) Battery module charging animation is disabled.
f) Flip calendar day switching animation is disabled.
g) Moon module image is only refreshed once per hour instead of every 3 minutes.

2. All modules that usually update once per second start updating every 2 seconds.

3. Clock module is only updated every minute instead of every second.

Full Power Saving Mode:

1. In addition to everything already happening for Medium Power Saving mode, modules now only update once every 4 seconds.

###

This is just what I managed to come up with so far. There is a lot more that can be done throughout the application, but the module update rate - and disabling cosmetic animations - is, without a doubt, what will have the most impact. Pity there is no easy way to measure it.

Besides decreasing the modules update rate, I wonder what else should be reserved to the highest power saving mode. The idea is that the Medium Power Saving Mode is something the user would want to *voluntarily* activate the second his laptop starts running on battery, so it should have a noticeable effect but not be so restrictive that the user would not want to activate it unless his battery was almost critical.

For instance, what about the Shelf expanding/collapsing, sub-dock opening, etc, animations: in which mode should those be disabled?

Any ideas? This is always easier with feedback from you guys.

For instance, what about the Shelf expanding/collapsing, sub-dock opening, etc, animations: in which mode should those be disabled?

1. All cosmetic animations are disabled. This means:

do those come up enough and use enough resources to make any difference?

if so, how big an impact do they have?

what about sounds? when should all non critical sounds be turned off

But if you turn off, say, the Shelf expand/collapse animation, the associated sound effect also goes with it.

So, the real question must become: would disabling those animations be something that would make the user prefer NOT to activate the medium power savings mode? If so, then it should be moved to full power savings mode.

but somehow it feels like something for full savings mode to me