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
When using a high-resolution display with Windows scaling enabled, the taskbar-monitor widget's UI elements overlap, making it difficult to read and use. This issue occurs on a 3840x2400 display with 250% scaling enabled.
Steps to reproduce:
Install taskbar-monitor on a system with a high-resolution display (e.g., 3840x2400)
Set Windows display scaling to a high value (e.g., 250%)
Observe the taskbar-monitor widget
Current behavior:
The UI elements of the widget overlap each other, making the information unreadable. CPU, MEM, DISK, and NET labels are stacked on top of each other, and the usage bars are not properly aligned.
Expected behavior:
The widget should scale appropriately, maintaining readability and proper layout at all display scaling factors.
TL;DR
When using a high-resolution display with Windows scaling enabled, the taskbar-monitor widget's UI elements overlap, making it difficult to read and use. This issue occurs on a 3840x2400 display with 250% scaling enabled.
Steps to reproduce:
Current behavior:
The UI elements of the widget overlap each other, making the information unreadable. CPU, MEM, DISK, and NET labels are stacked on top of each other, and the usage bars are not properly aligned.
Expected behavior:
The widget should scale appropriately, maintaining readability and proper layout at all display scaling factors.
Screenshots:
Tested Environment:
Windows version: Windows 10, version 21H2
NET Framework Setup
Returns
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full Release REG_DWORD 0x8234d
533325 (
0x8234d
) is greater than 533320, which means I must have .NET Framework 4.8.1 installed on my systemDisplay resolution: 3840x2400
Display scaling: 250%
taskbar-monitor version: v0.4.2
Question:
Are there any current workarounds or configuration options that might help address this issue in the short term?
I'd be happy to provide any additional information or assist with testing if needed.
The text was updated successfully, but these errors were encountered: