Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Increase size of the "Charge %" bar in the battery widget #1238

Closed
1 task done
FreezyLemon opened this issue Jul 2, 2023 · 1 comment · Fixed by #1251
Closed
1 task done

Increase size of the "Charge %" bar in the battery widget #1238

FreezyLemon opened this issue Jul 2, 2023 · 1 comment · Fixed by #1251
Labels
feature Requests for a new feature. good_first_issue An issue that should be pretty easy to resolve, even for a first-time contributor.

Comments

@FreezyLemon
Copy link

Checklist

Describe the feature request

The battery widget currently seems to be split 50/50, with the left side being labels for the information shown on the right side:

image of the battery widget

I'm not sure how easy "breaking" this column-based layout is, but IMO it would make sense to give the "Charge %" bar more horizontal space.

Otherwise, maybe give the bar its own line?

Charge %
[||||||||||                         37%]

Rate                  12.34W
State                 Discharging
To empty              3h 17m 12s
Health %              97.00%
@FreezyLemon FreezyLemon added the feature Requests for a new feature. label Jul 2, 2023
@ClementTsang
Copy link
Owner

Hm, could look at that.

@ClementTsang ClementTsang added the good_first_issue An issue that should be pretty easy to resolve, even for a first-time contributor. label Jul 2, 2023
@gabelluardo gabelluardo mentioned this issue Jul 9, 2023
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Requests for a new feature. good_first_issue An issue that should be pretty easy to resolve, even for a first-time contributor.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants