GNOME Bugzilla – Bug 769598
Add option to show Battery percentage in Top Bar
Last modified: 2017-07-02 12:02:20 UTC
In Gnome 3.20, the Battery Percentage can be shown with: gsettings set org.gnome.desktop.interface show-battery-percentage true Please add this option to Tweak Tool.
You can access it from dconf editor, FWIW. But if this is a really common request, then it should be in the most discoverable place: gnome-control-center. Or even enabled by default.
Created attachment 353243 [details] [review] Add battery percentage on top bar
Review of attachment 353243 [details] [review]: Thank you for working on this bug and submitting a patch. Unless you hear different from Design, I think I'd prefer this setting in the Top Bar page. How about a "Battery Percentage" switch under a Power heading there? By the way, git master has been converted to python3 and meson now.
Created attachment 353289 [details] [review] Add battery percentage switch under top bar section
Thank you. I have pushed this now. I made two small changes: 1. I capitalized "Percentage" to match the other labels in the Top Bar panel. 2. I added this bug number to the git commit description. It can be added automatically if you use something like git bz attach -e 769598 http://git.fishsoup.net/man/git-bz.html http://git.fishsoup.net/cgit/git-bz/tree/git-bz By the way, I intend to push a new gnome-tweak-tool 3.25 release today because I want to get some of these new features in Ubuntu 17.10 Alpha.
Note taken for possible next contributions
Alberto, could you please update the Top Bar panel to match the mockup that was updated today? https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/tweak-tool/tweak-tool-wires.png
hands on it
Created attachment 353703 [details] [review] Reorder Top bar components I found the only change is components order, am I right? I don't know if mark prior patch as obsolete since it is committed
I adjusted the first line of the commit message to better match the commit style and pushed this for you. Thank you! There was no need to mark the other commit as obsolete since this one applies on top of that one. By the way, I marked a few bugs for newcomers.
*** Bug 784304 has been marked as a duplicate of this bug. ***