https://bugzilla.novell.com/show_bug.cgi?id=299626#c7 --- Comment #7 from Maciej Pilichowski <bluedzins@wp.pl> 2007-08-13 13:50:19 MST --- Andreas, all changes are made in kpowersave. I used originally KControl but since it just calls kpowersave you can ignore this step and use KPowersave directly. To summarize -- my concern is that you can (and I do) change some things directly from popup menu. But you can also go to configuration and change (like in this example) monitor settings and _nothing_ else. But when you commit it, you see that all options, even those you didn't see are changed! 1) this is simply bad UI/design -- compare it to KControl, only those things which you changed are changed (well, by definition almost) 2) I would suggest to fix the UI because it is the root of the problem -- either by providing commit on every tab/page or by changing only this what was change 3) or reading current values and suggesting them, so you could skip any changes in UI 4) or don't change current option after scheme changes if they differ 5) or ... :-) Simply put -- problem is Kpowersave mixes (with bad result) settings "for now" with settings "for scheme". Problem exists and it would be good to solve it. Of course Danny can say he is maintainer and I am just a user of no importance and he is right (no irony here) -- but I am familiar with a good design principles and the principle of the least surprise is one of them. KPowersave does not follow it. Thank you for listening. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.