-
Notifications
You must be signed in to change notification settings - Fork 171
[FIXED] Watch list bug #82
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
Comments
upgrade your Windows |
Why do you close issue without confirmation from the applicant? Case is not resolved yet. |
sadly Windows 10.... yes... I've accepted that it wouldn't "work" for Windows 2000 or XP... but also found it surprising that even Windows 7 failed... And since there's no way for me to fix it and just a minor graphical "glitch" (but still better than nothing) I'll leave it as is. I might consider to add the smaller variant even though you're unlikely to determine if they're up or down, once the next version hits because it got more such list views with sorting. And if nothing works... I might use P.S. thanks for your persistence... |
Actually I’m quite surprised. Being a beta tester for a couple of decades (since FIDO times), I could hardly recall another native Windows tray app without cross-platform GUI dependencies (like QT) that would introduce an obstacle related to rendering labels. Support of XP is dropped by Microsoft, but 7 is far from death and is the current choice of the majority, therefore users are entitled to expect no visual glitches, so obviously we should revise the appearance of T-Clock watch list. |
like I said.. it's a Windows issue... and I'm not willing to figure out some workarounds with dozen lines of code just to waste my time and bloat the app.... I don't know why Windows isn't able to render it properly, nor a way to fix it (unless I'll render it entirely myself but that's a lot of work) |
just to keep you updated... the small version released today doesn't include a Workaround for a Windows older than 10... It's mostly a bug fix release and the mentioned UI update isn't ready yet. Though, I also need to mention that MSVC builds seem to be broken anyway... Somehow the compiler isn't able to handle UTF-8 encoded files... |
What do you mean? I have unpacked latest (2.4.3) static build and executed Clock64.exe without errors. |
the "_static" is build by GCC while those 2 other archives are build by MSVC. I don't know yet how to fix my MSVC builds.. I don't really like to add a UTF-8 BOM to all my source files... (might break Github, breaks old GCC but shouldn't break my build system) and VS2010 doesn't seem to support any command switch like |
…ixes #82) ! fixed UTF-8 related issues with MSVC compilers, which resulted in broken characters. this includes the use of universal character names, redundant BOM removal (alarm.c)
Here you go: v2.4.4 |
Eventually, the solution is found. Bravo! |
Uh oh!
There was an error while loading. Please reload this page.
Could you be so kind to eliminate unknown characters next to “Remaining” label?
The text was updated successfully, but these errors were encountered: