https://bugs.kde.org/show_bug.cgi?id=393956
--- Comment #15 from pallaswept <pallasw...@proton.me> --- Just to set expectations for future users of this here, I have found some limitation to Qt's time formatting: You can't have 12-hour time, without an AM/PM identifier, or 24 hour time, with one. The API returns a time in 24 hour time if there is no AM/PM, or 12 hour if there is one. So for example, if you wanted 10 o'clock at night to be shown as "10:00" or "22:00PM" ... Too bad. You can have "22:00" or "10:00pm" or "10:00PM". Similarly, you can't change the am/pm designator. So like you can have "10.00PM" or "10.00pm" but you cannot have "10.00p" or "10.00 at night" I could work around this through various means but... it's a MASSIVE jump in complexity, not that I mind, but I feel like it's a bad idea. It definitely seems like scope-creep into an artistic clock rather than a utility. I feel like if we really want this, it should be done by enhancing the Qt APIs to support it (after which it would 'just work' here without further changes) So, I guess if you really wanted one of those unusual time formats, please do start now with trying to have it added upstream. Apologies if this is a letdown for anyone. I figure it's unlikely to be a problem, but what do I know ;) Please feel free to speak up if this is a major problem for you. Oh one other thing - if you show milliseconds, it still only updates every ~1 second. I don't see this as a problem really. I mean... lol. I tested it to be sure it wouldn't break, but I don't expect to get that working. Again, if this is a big deal for you, please sing out! PS Thanks again Justin :) I've just found out that I social media so rarely that my matrix account was seen as abandoned and is gone forever, so I'll make a new one and be by in a few hours when the Western Hemisphere is awake :D -- You are receiving this mail because: You are watching all bug changes.
