8000 time update not occurring unless t-clock gains or loses focus · Issue #1 · White-Tiger/T-Clock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

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

Closed
rodolbud opened this issue Mar 18, 2015 · 19 comments
Closed

time update not occurring unless t-clock gains or loses focus #1

rodolbud opened this issue Mar 18, 2015 · 19 comments
Labels

Comments

@rodolbud
Copy link

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".

@White-Tiger
Copy link
Owner

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?

@rodolbud
Copy link
Author

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.
OS = Windows 7 (Enterprise) 64-bit with Service Pack 1.

@White-Tiger
Copy link
Owner

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...
Anyway, does this problem exist from the very beginning, or did it happen after some time?
Was there any T-Clock version that you know that worked?

@rodolbud
Copy link
Author

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.

@White-Tiger
Copy link
Owner

well... will try to reproduce it the following days, using a virtual Win7 machine.

@White-Tiger
Copy link
Owner

might take a few more weeks, don't have enough disk space to setup a VM right now...

@White-Tiger
Copy link
Owner

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?
Right now I have literally no clue :P I could understand if the clock display freezes after some time, or a stand-by / hibernate, but not really from the very beginning and then working on mouse over, etc.

@White-Tiger
Copy link
Owner

Any special settings that differ from vanilla Windows?
So, any classic themes, XP style, custom themes? Anything that might mess with the window system?

@White-Tiger White-Tiger removed the bug label Apr 13, 2015
@biltong11
Copy link

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.
Win 7 Pro, 64 bit. No themes or other Windows mods.

@White-Tiger

PC always running 24/7 or does it go to sleep/hibernate from time to time?

@hspindel
Copy link

I also experience time update not occurring. Computer runs 24/7, never
sleeps/hibernates.

On 7/30/2015 1:42 AM, René Schümann wrote:

PC always running 24/7 or does it go to sleep/hibernate from time to time?


Reply to this email directly or view it on GitHub
#1 (comment).

@White-Tiger
Copy link
Owner

I guess simply exiting T-Clock and starting it again also temporarily "fixes" this issue? @biltong11 said you'll reboot to "fix" it...

@biltong11
Copy link

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.

@hspindel
Copy link

Closing and reopening fixes it for me.

On 7/30/2015 2:52 PM, biltong11 wrote:

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.


Reply to this email directly or view it on GitHub
#1 (comment).

@biltong11
Copy link

I have had the issue occur again, and I can confirm closing and reopening does indeed fix the problem.

@White-Tiger
Copy link
Owner

can you guys test my latest pre-release ?
Not sure if it is fixed, if not: try to rightclick->"Refresh T-Clock" and report back if that causes it to refresh again..

@biltong11
Copy link

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!

@White-Tiger
Copy link
Owner

It's a regression... if you had a 32bit OS, you wouldn't even notice xD
But it likewise also kills the multi-monitor support the same way.. (that is, Windows' inbuild calendar should be centered on non-primary monitors..)

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:
and there it is, an issue #14 (was hoping to not get one xD Though I should probably put a note on said release so ppl. know about that issue beforehand...)

@White-Tiger
Copy link
Owner
White-Tiger commented Aug 3, 2016

closing for now. Please reopen when it happens again.

4A9E
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants
0