-
Notifications
You must be signed in to change notification settings - Fork 171
time update not occurring unless t-clock gains or loses focus #1
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
is your format related to this problem? Or does it also occur when you disable the "Custom Format" checkbox (don't worry, you will not loose your custom format unless you change the locale^^ But that's a bug) Also: what OS do you use? |
i tried unchecking the "Custom Format" (btw - I did lose my custom format, but anyway). Unchecking the Custom Format did not help the problem - it still exists. |
by "won't loose" I've meant that T-Clock will remember your custom format and you can safely enable it again... at least should be... |
RE: "Won't lose" - you are correct, when I re-enabled it, it re-remembered by format. This is the only White Tiger version that I have installed. I have not had it for very long, so likely (although I cannot confirm), it has done it since installation. I had previously installed a Stoic Joker version (32-bit running on Windows 7 32-bit), but this problem did not occur with that version. I forget the version number of the Stoic Joker version, and my computer has since been "wiped" and re-imaged with 64-bit Win7. |
well... will try to reproduce it the following days, using a virtual Win7 machine. |
might take a few more weeks, don't have enough disk space to setup a VM right now... |
well.. just tested on a Win7 Ultimate and everything seems to work as it should... so clock refreshes, etc. so right now, I can't reproduce it... Could you maybe boot your Windows into safe mode and run T-Clock there? |
Any special settings that differ from vanilla Windows? |
I also experience this issue with the clock not updating - but not all the time. If I reboot, the problem clears and the clock works fine. I cannot identify at what point it stops working, but usually after a few days and the PC hasn't been rebooted. |
PC always running 24/7 or does it go to sleep/hibernate from time to time? |
I also experience time update not occurring. Computer runs 24/7, never On 7/30/2015 1:42 AM, René Schümann wrote:
|
I guess simply exiting T-Clock and starting it again also temporarily "fixes" this issue? @biltong11 said you'll reboot to "fix" it... |
To be honest I am not sure whether closing and opening T-Clock will fix it. Rather silly, but I don't think I have tried that. I haven't had the issue this week so far, but will certainly try it when it happens again. To answer the previous question - no sleep or hibernation. |
Closing and reopening fixes it for me. On 7/30/2015 2:52 PM, biltong11 wrote:
|
I have had the issue occur again, and I can confirm closing and reopening does indeed fix the problem. |
can you guys test my latest pre-release ? |
So far so good! Since updating I have not had the problem again, but I will continue monitoring. (One thing I have noticed with the new version - the calendar opens up in the centre bottom of the screen, whereas before it would always open bottom right above the clock. I cannot fin any option to change this behaviour. Is this by design? If not, do I open a new issue?) Thank you for your efforts with this fantastic software! |
It's a regression... if you had a 32bit OS, you wouldn't even notice xD I've actually seen this "issue" before you and another reported it.. hope you can live with this in the mean time... I might push a new version next week if that's ok with you Probably also enough time for this issue here to "verify" :P edit: |
closing for now. Please reopen when it happens again. |
I am using 64-bit 2.3.2 build 151. I am experiencing an issue where the time is not updating unless t-clock gains or loses focus in the system tray. I am using "Custom Format" on "Time Format" tab as "dddd\nmm/dd/yyyy\nhh:nn:ss".
The text was updated successfully, but these errors were encountered: