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

Time applet should use a monospace font #635

Open
wiiznokes opened this issue Aug 30, 2024 · 4 comments · May be fixed by #688
Open

Time applet should use a monospace font #635

wiiznokes opened this issue Aug 30, 2024 · 4 comments · May be fixed by #688

Comments

@wiiznokes
Copy link
Contributor

This is even more visible with the show second option

@bbb651
Copy link

bbb651 commented Aug 31, 2024

It's should be simple to change it to cosmic::font::FONT_MONO_REGULAR (which is Fira Mono), I don't think it'll look out of place compared to the default font (Fira Sans). Although when I tried it with .font(cosmic::font::FONT_MONO_REGULAR), it doesn't seem to find it and fallbacks to a different font, but I'm also getting no warnings or errors at all so I'm not sure:

image

image

Also apparently I found a bug where the screenshot continues to the wrong monitor, I have two monitors and secondary one is to the right of the primary, but after moving the mouse too much left in the selection it captured the right area of the right screen (if this is intended to wrap around like that, there's currently no visual indication that it's happening).

@wiiznokes
Copy link
Contributor Author

it might not be a good idea to hardcode a font like that if they want to make fonts configurable

@WatchMkr
Copy link

Perhaps an option to use monospace font in the Time applet settings UI that is on the roadmap.

@wiiznokes
Copy link
Contributor Author

I don't think an option is necessary. Why not use a mono font by default?

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

Successfully merging a pull request may close this issue.

3 participants