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
So far I used this great app with an 1920x1080 monitor with 100% scaling (windows setting), but after switching to a 4k monitor (resolution: 3840x2160) with 200% scaling, the remaining time on the system tray icon became mostly useless because it is scaled to be too big.
Examples:
3840x2160 100% scale (great ✅):
3840x2160 150% scale (issue starts to be visible):
3840x2160 200% scale (timer is not visible):
(Personal note: As I can't find a workaround for this and the main reason I chose YAPA 2 for my pomodoro app was this exact feature of showing the remaining time as a system tray icon, I have to start looking for an alternative. ☹️ )
Tech details for reproduction:
Windows version: (cmd: winver): Version 21H2 (OS Build 22000.2538)
Screen resolution: 3840x2160
Windows scaling: 200%
The text was updated successfully, but these errors were encountered:
arphox
changed the title
[System tray plugin] Reamining time gets unreadable on system tray icon due to wrong scaling
[System tray plugin] Remaining time gets unreadable on system tray icon due to wrong scaling
Apr 2, 2024
Hi!
So far I used this great app with an 1920x1080 monitor with 100% scaling (windows setting), but after switching to a 4k monitor (resolution: 3840x2160) with 200% scaling, the remaining time on the system tray icon became mostly useless because it is scaled to be too big.
Examples:
3840x2160 100% scale (great ✅):
3840x2160 150% scale (issue starts to be visible):
3840x2160 200% scale (timer is not visible):
(Personal note: As I can't find a workaround for this and the main reason I chose YAPA 2 for my pomodoro app was this exact feature of showing the remaining time as a system tray icon, I have to start looking for an alternative.☹️ )
Tech details for reproduction:
winver
): Version 21H2 (OS Build 22000.2538)The text was updated successfully, but these errors were encountered: