Tray icons move around when "Show seconds on the taskbar clock" is enabled

from Stardock Forums

With the "Seconds on the taskbar clock" option turned on...

Because the number "1" is "skinnier" than the other numbers, whenever the number "1" appears in the time, the width of the clock changes.  This causes the position of the system tray icons to change and there is some flickering while they are redrawn.  (Maybe this is easier to see at 200% DPI which is what I am running on.)

This can be seen for example when the "seconds" part of the clock cycles through 09... 10... 11... 12.  Each one of these has a different number of "1"s and changes the width of the clock.

Maybe the clock container could be made to be a fixed width?  Or there could be an option to change the font so that it could use a proper fixed-width font?

Thanks for consideration.

start menu products
19,110 views 8 replies
Reply #1 from Stardock Forums Top

Hello,
Sorry to hear you are having issues. Need to know more on your system.

  1. You on Windows 10 or 11? And also need to know its full version numbers. Use Winver.exe to get it.
  2. Start11 version installed?
  3. Need to know how did you add seconds to your taskbar clock?

Thanks
Basj,
Stardock Community Assistant.

Reply #2 from Stardock Forums Top

Windows 11.  22621.382.  (22H2 update that just came out today.)

Start11 version 1.25.

I know how to enable seconds on the clock.  I have an issue when seconds are enabled (see above).  The width of the clock changes and it causes the positions of the tray icons to the left of the clock to change (with flickering).

Groupy 2 - Organize multiple applications into grouped tabs on your Windows desktop
Reply #3 from Stardock Forums Top

Yes, I knew you know, but I need to know it too. So I can try to reproduce it on my end.

Thank you,

Basj,
Stardock Community Assistant

Reply #4 from Stardock Forums Top

This has been reproduced in house and is caused by using very short date formats which mean the clock text length exceeds the date text sometimes.

We have made some changes for v1.26 which should resolve this which is due for release soon.

Reply #5 from Stardock Forums Top

Quoting basj, reply 3
Yes, I knew you know, but I need to know it too. So I can try to reproduce it on my end.

Sorry, I misunderstood you.  It's a checkbox in the taskbar settings in Start11 Configuration.  It only shows up if you are on Windows 11 (2022 update / version 22H2), not earlier versions or Windows 10.

Quoting Neil, reply 4
This has been reproduced in house and is caused by using very short date formats which mean the clock text length exceeds the date text sometimes.

We have made some changes for v1.26 which should resolve this which is due for release soon.

Thank you, I will look forward to the next release.

Reply #6 from Stardock Forums Top

Quoting Aaron44126, reply 5

Sorry, I misunderstood you. It's a checkbox in the taskbar settings in Start11 Configuration. It only shows up if you are on Windows 11 (2022 update / version 22H2), not earlier versions or Windows 10.
I'm on Windows 10... just saying.

Reply #7 from Stardock Forums Top

Quoting JanOscar, reply 6
I'm on Windows 10... just saying.

OK, cool, I guess they added it on Windows 10 as well.  Windows 10 taskbar already supports seconds in the taskbar clock via a registry setting (which I have been using for years), so I guess I never looked at Start11...

Start11 is not supporting seconds-on-the-taskbar for the original (21H1) Windows 11 release.  So at least on the Windows 11 side you'd have to upgrade to 22H2.

+1 Loading…
Reply #8 from Stardock Forums Top

Quoting Aaron44126, reply 7


Quoting JanOscar,
reply 6
I'm on Windows 10... just saying.



OK, cool, I guess they added it on Windows 10 as well.  Windows 10 taskbar already supports seconds in the taskbar clock via a registry setting (which I have been using for years), so I guess I never looked at Start11...

Start11 is not supporting seconds-on-the-taskbar for the original (21H1) Windows 11 release.  So at least on the Windows 11 side you'd have to upgrade to 22H2.

Correct yes.  It is supported on 22H2 and Windows 10 but not 22H1.