You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running TClock-Win10 Ver 5.4.1.1 on Windows 11 Professional 23H2.
Issue 2) where the full system traybar overflows over the system tray notification icons is in need of a solution other than exiting the T-Clock appication to resolve.
Issue 1) is cosmetic in appearence, if the T-Clock height could be adjusted to reveal the boarder line, or the ability to just move the T-Clock a few pixels downward?
Other than that, T-Clock v5.4.1.1 would be acceptable on Windows 11 23H2. Lots of Window end users prefer having a bigger adjustable clock in the system traybar to see, compared to the tiny size of the default Windows clock. Why hasn't Microsoft in all these years supported a most obvious need - like for the eldely who's vision would benefit for a larger customizable view of the clock/date?
Thank you MantisMountainMobile in advance for considering to resume support - just in case. :-)
The text was updated successfully, but these errors were encountered:
I'm running TClock-Win10 Ver 5.4.1.1 on Windows 11 Professional 23H2.
Issue 2) where the full system traybar overflows over the system tray notification icons is in need of a solution other than exiting the T-Clock appication to resolve.
Issue 1) is cosmetic in appearence, if the T-Clock height could be adjusted to reveal the boarder line, or the ability to just move the T-Clock a few pixels downward?
Other than that, T-Clock v5.4.1.1 would be acceptable on Windows 11 23H2. Lots of Window end users prefer having a bigger adjustable clock in the system traybar to see, compared to the tiny size of the default Windows clock. Why hasn't Microsoft in all these years supported a most obvious need - like for the eldely who's vision would benefit for a larger customizable view of the clock/date?
Thank you MantisMountainMobile in advance for considering to resume support - just in case. :-)
The text was updated successfully, but these errors were encountered: