Skip to content
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

UI elements overlap at high display scaling factors #56

Open
WSHAPER opened this issue Sep 17, 2024 · 0 comments
Open

UI elements overlap at high display scaling factors #56

WSHAPER opened this issue Sep 17, 2024 · 0 comments

Comments

@WSHAPER
Copy link

WSHAPER commented Sep 17, 2024

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:

  1. Install taskbar-monitor on a system with a high-resolution display (e.g., 3840x2400)
  2. Set Windows display scaling to a high value (e.g., 250%)
  3. 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.

Screenshots:

image

Tested Environment:

  • Windows version: Windows 10, version 21H2

  • NET Framework Setup

    reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Release

    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 system

  • Display 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.

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

No branches or pull requests

1 participant