I think that it should be separate, otherwise every time I'm on battery and happen to change the brightness, the next time I switch from AC to battery it's going to now go to this new value that I didn't explicitly set. What's worse, when I go into g-p-m's config, I'll see that the slider has changed since the last time that I set it, to a value that I didn't explicitly set. I think in general programs shouldn't change values behind the scenes that a user explicitly set. If this value is going to always move according to the current brightness level, then there's no need for a slider at all, since anything the user sets it to will ultimately be changed.
Maybe my use model is different from other people, but I purposely have the default backlight brightness for battery mode set to one step below zero. The point is that you can't really predict what your lighting is going to be when you switch to battery power, but if I have it set low by default, I can always increase it to suit my surroundings. If it were set relatively high by default (or worse, set to whatever arbitrary value it was set to last time I was on battery power), then at least psychologically a lower value might seem too dim, since I'm comparing it to a nice brighter value, which will always seem better, even if that low value might be fine to me if I jump right to it. I understand that for it to work this way you would need to create a new variable to store the current pre-idle backlight setting, but at least with the way I use it, it would create a more expected behavior. -- Backlight no longer under my control on battery https://bugs.launchpad.net/bugs/131885 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
