T-Clock
T-Clock copied to clipboard
White-Tiger
Second monitor Taskbar clock becomes misaligned over time.
Second Display: https://i.imgur.com/pYRxkAz.png
Primary Display: https://i.imgur.com/frKuCNv.png
I like my taskbars slim and out of the way, but with easy access to time/date. App Works great for that, but over time randomly as I tab in and out of fullscreen apps, Tclock becomes misaligned until the process and explorer are restarted.
The longer it goes on, the more it slides out of view until it can't be seen anymore.
Should note that it doesn't happen every time.
I have no idea what could be causing this one, but I've noticed windows explorer occasionally refreshes or reloads and my taskbar blinks for a moment. During that, it may be messing with T-Clock,
I think it's worth noting that; Settings>Clock Text> Size and Text position> "horizontal setting". It doesn't move based on the position of the taskbar's bottom. If I set it to 5 pixels, my monitor on the left moves it to the right 5px, while the monitor on the right also goes the same direction, always shoving one off of the screen, making my setup difficult to adjust.
This issue has been plaguing me for months. Requiring a restart of Explorer and T-Clock to fix.
I could upload my .ini file if that would help.
Edit; I'm able to repeat the glitch by resetting the graphics driver with the hotkey: Ctrl+Win+Shift+B
Having the same problem - hoping there are some current maintainers or folks interested. Hate to see this app die off.
Did you try the nightly version already? https://github.com/White-Tiger/T-Clock#downloads-binaries There's been a lot of injection / position changes since beta. Nothing new per se (as all of this happened in 2018) but I assume it would have fixed your problem. Alas, it works for me...
Positioning errors always happened since the Win 10 Anniversary update which required some hacky workarounds. So it might still not work in the end.
Did you try the nightly version already? https://github.com/White-Tiger/T-Clock#downloads-binaries There's been a lot of injection / position changes since beta. Nothing new per se (as all of this happened in 2018) but I assume it would have fixed your problem. Alas, it works for me...
Positioning errors always happened since the Win 10 Anniversary update which required some hacky workarounds. So it might still not work in the end.
I'm on the beta, I'll give the nightly a try. (Never really knew there was a difference.) Still hoping for some new blood. 😅
@White-Tiger It's looking like the nightly might've fixed it, I haven't noticed the problem yet today.
@White-Tiger I spoke too soon - the problem is still happening with the Nightly version.
But you don't know how to reproduce it? I assume it might happen after hours of use?
Does right click->Refresh T-Clock do anything when it's off set?
Yes, refreshing it fixes it. I assume it's just an "over time" thing, like OP said. It MAY happen/begin when switching applications, I only notice it after not looking at it for a while when playing games etc., and after a while I don't see the clock.
But the display resolution etc. don't change when I do that, so unless it's something to do with fullscreen apps, that might not be.
On Mon, Jan 9, 2023 at 2:58 PM René Schümann @.***> wrote:
But you don't know how to reproduce it? I assume it might happen after hours of use? Does right click->Refresh T-Clock do anything when it's off set?
— Reply to this email directly, view it on GitHub https://github.com/White-Tiger/T-Clock/issues/281#issuecomment-1376304602, or unsubscribe https://github.com/notifications/unsubscribe-auth/AFJ3TTMVMFCONGDCAMLPYITWRR3YDANCNFSM6AAAAAARIQTQBM . You are receiving this because you commented.Message ID: @.***>
@White-Tiger I forgot to mention this from a while ago: I disabled ClearType (or rather, changed the Text Quality to Default - either way ClearType is off) and I think that fixed it on my Win10 machine. I haven't noticed the need to reset the clock lately.
I'll test that... I've personally been using "ClearType Natural" but switched to the ugly XP one now just on case :P
Oh is it "ClearType WinXP+" generally not supposed to be used? Both of my machines have had that selected since install. I'll have to do some more testing too it seems.