mirror of
https://github.com/1Remote/1Remote.git
synced 2026-04-25 13:36:03 +03:00
[GH-ISSUE #1051] Incorrect scaling behavior when I drag the 1Remote window to a monitor with a different scaling factor | 有多个缩放比不同的显示器时, 软件无法正常感知当前所在显示器的缩放率 #1788
Labels
No labels
area-configuration
area-ct-app
area-ct-rdp
area-ct-remoteapp
area-ct-ssh
area-ct-vnc
area-launcher
area-list
area-tags
area-teamwork
bug
chore
dependencies
general-build/ci
general-performance
general-refactor
general-security
general-supportive
general-ux
meta-documentation
meta-enhancement
meta-enhancement
meta-feature
meta-help-wanted
meta-unknown-error
priority-hi
priority-low
pull-request
question
resolution-duplicate
resolution-invalid
resolution-wontfix
stale
task-put-off
task-still-considering
task-working-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/1Remote#1788
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @BH2WFR on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/1Remote/1Remote/issues/1051
Originally assigned to: @VShawn on GitHub.
Describe the bug
My main monitor is 150% scaling, and the second monitor is 100% scaling. When I launch 1Remote in the main monitor with 150% scaling and drag the window to the 100% scaling monitors, it seems like it doesn't modify and re-draw the window with a new scaling factor, and the window just be drawn as 150%, and simply zoomed out to 100%, causing screen content a little blurred. (the GUI cannot aware the DPI of located monitor).
我的主显示器是 150% 缩放比, 而副屏是 100% 缩放比. 我在主显示器启动了这个软件, 然后拖动到副屏, 发现窗口并没有被重新调整 scailing, 而是以 150% 渲染后强行 "缩小" 到 100%, 看上去界面比较模糊. (也就是软件无法检测到窗口所在显示器的 DPI 信息)
When I start a RDP connection ("auto scaling turned on", and using built-in window), the remote display always keeps 150% scaling, and cannot automatically re-scail to 100% when I drag the window to the second monitor with 100% scaling factor.
在这种状态下, 我启动一个 RDP 连接, 然后将窗口拖动到副屏, 可以看到远程连接的 缩放率并没有改到 100%, 而是仍然维持 150%, 然后被 "缩放" 到 100%, 造成显示效果不佳.
Expected behavior
The window is better to be automatically re-scailed when I move to the other monitor with a different scaling factor by the main monitor, including that of RDP connection.
Desktop (please complete the following information):
@VShawn commented on GitHub (Jan 5, 2026):
i am not sure if we can set the scale on fly, I will try it out.
@itagagaki commented on GitHub (Jan 6, 2026):
Usually, when you drag a window between displays with different scaling, the window's overall drawing scaling changes once it passes the center point. 1Remote's windows seem to behave the same way. Is there a problem?
@VShawn commented on GitHub (Jan 9, 2026):
If you mean the scaling ratio of the entire interface changes, then this is normal. This change is automatically controlled by Windows app DPI-Aware feature (to be honest, I’m not familiar with the technical details behind it).
As for RDP’s scaling ratio, it requires actively calling the code
_rdpClient.SetExtendedProperty("DesktopScaleFactor", _primaryScaleFactor);to take effect. In 1Remoete, I only execute SetExtendedProperty("DesktopScaleFactor") in theRdpInitDisplayfunction when starting the connection, so when moving to another screen, the RDP scaling ratio does not change accordingly.I am currently investigating #1053. I need to finish #1053 before I can follow up on this ticket.
@itagagaki commented on GitHub (Jan 9, 2026):
Yeah, I wanted to say that.
And the RDP scaling ratio also seemed fine in my tests.
But if you already know what the problem is, that's good ;-)
@VShawn commented on GitHub (Jan 12, 2026):
yes I know the problem is, What i am not sure is that
if we can set the scale on fly. I will try it out later.P.S. Babysitting now takes most of my spare time, so progress might be slow.
@github-actions[bot] commented on GitHub (Feb 12, 2026):
This issue is stale because it has been open for 30 days with no activity.