Bug 456916 - analogue plain complete clock widget?
Summary: analogue plain complete clock widget?
Status: RESOLVED INTENTIONAL
Alias: None
Product: Oxygen
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 5.25.3
Platform: unspecified All
: NOR wishlist
Target Milestone: ---
Assignee: Unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-07-19 14:38 UTC by David Chmelik
Modified: 2026-02-13 07:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
hard-to-read clock (69.25 KB, image/jpeg)
2022-07-19 14:38 UTC, David Chmelik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Chmelik 2022-07-19 14:38:24 UTC
Created attachment 150739 [details]
hard-to-read clock

SUMMARY
Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.)

STEPS TO REPRODUCE
1. Add analogue clock widget.
2. Sometimes have trouble reading it.

OBSERVED RESULT
Analogue clock widget misses most numbers (and the dark theme one has distracting pattern in it.)

EXPECTED RESULT
Option to have all numbers (preferably outside absolute position marks) and option for just black on white (Air light Oxygen theme) and plain (no pattern) white/light-grey on black (Oxygen dark theme).

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: FreeBSD UNIX 8-13, KDE Neon 5 & Slackware 13-15 GNU/Linuxes
KDE Plasma Version: 4, 5
KDE Frameworks Version: 4, 5
Qt Version: 4, 5
Comment 1 Filip Fila 2026-02-13 07:44:40 UTC
I'm worried that having all of the numbers on by default would be too cluttering. And from the point of view of Oxygen and Air we can only change this default look.

Having all of the numbers as an option would mean having to patch the clock widget itself, which I'm not sure would be accepted. Technically it might mean having to load an entirely new SVG since we can't just add numbers to the existing clock.svg, but also have to replace the placeholder marks.

I see your concerns, but unless I see a clear way of how to move this forward, I don't think we can implement this.