Digital Clock 4

ver.4 is not recommended as it is built with old tools, and who knows how it will behave in new environment, especially with HighDPI displays. know nothing about MS Edge downloads, maybe this something about SourceForge and how it works in MS Edge, or maybe just because my installer is not signed and MS enforces signed installers even there. Firefox never complained. unsigned installer is also the reason why Windows shows warning on run/install.

thanks for the review. what about questions/suggestions, contact me by email or create issue/discussion on GitHub and provide more details. it is not so clear what you want to see.

thanks for the review! the mentioned faded segments are part of the skin, I'll include new skin without them in the next version, as some users contacted me with the same complaints

I understand that alarm is quite important feature, but unfortunately this is unlikely be added because it will be completely useless and unreliable. nowadays most of the systems (especially Windows) goes to "deep sleep" mode if computer "left alone", in this case the only working time source is RTC (hardware clock), and only low-level OS stuff has access to it, whatever apps are just doesn't work. so, implementing alarm clock in regular app is just unreliable - it will not do its job if computer will be in sleep mode. the only only way I see - to use system-provided clock/alarm apps for that purpose, but also test them several times before "relying on them", as who knows what's behind them (especially taking into account various "sandbox" technologies common for "app-store apps"). and it is very unlikely that the regular app can get access to RTC, and even more somehow wake-up computer when it needs, such operations are privileged by design, only very few system-specific utilities can get access to it. preventing sleeping is not an option, and this is also will be privileged operation too. and who wants to run some small unknown 3rd-party app in privileged mode or have some hidden privileged system services running for that purpose (this is a common hack nowadays)? so, all these things lead to very complicated platform-specific implementation and still provide almost no reliability, hence it just doesn't worth (especially taking into account the fact that I'm not a Windows developer).

thanks for the review! there is an option that controls clock behavior in full screen mode ("show in fullscreen mode"), you can can disable it, then clock will not appear in fullscreen apps (at least it should). unfortunately, it is too problematic to implement some global hotkeys, library I used for this purpose previously seems not maintained anymore and barely usable now.