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

[bug] Make clock width constant when seconds are visible #684

Closed
vancha opened this issue Oct 14, 2024 · 3 comments
Closed

[bug] Make clock width constant when seconds are visible #684

vancha opened this issue Oct 14, 2024 · 3 comments

Comments

@vancha
Copy link

vancha commented Oct 14, 2024

Cosmic-applets version:
0.1.0172887823022.04~7b005f9

Specific applet that this is regarding (if applicable):
'Date, Time & Calendar'

Issue/Bug description:
The issue I seem to be having with the cosmic clocks is that when I have enabled the seconds for the clock widget, other applet icons in the panel shift when the clock ticks. E.g, when the time is 11:11:11 the width of the clock widget is smaller than when it' s 00:00:00. So with every second, the applet icons shift around

Steps to reproduce:
click the Date & time applet, then select settings. Select "Date & Time", and check the "Show seconds" setting. If you have multiple applet icons in your panel you should see them shift around (try adding multiple applets to the end segment in your panel, and make the clock the rightmost one).

Expected behavior:
I think the expected behavior would be that regardless of the exact time the applet displays, the width should be constant. Changes in the time should not cause the other applet icons to shift.

@wiiznokes
Copy link
Contributor

wiiznokes commented Oct 15, 2024

Same of #635. This is indeed an annoying one, i worked around it by moving the applet to the right of the left part of the panel.
It should be easy to fix with the recent libcosmic change concerning font 🤔

@vancha
Copy link
Author

vancha commented Oct 15, 2024

Apologies for creating a duplicate issue, that is indeed exactly what I am referring to too! Ill try your workaround, thanks ;)

@leviport
Copy link
Member

No worries. Closing as a duplicate of #635

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants