[GH-ISSUE #757] The capture region can't be moved across multiple displays when using the new recorder experience #609

New issue

Open

opened 2026-02-26 09:32:03 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 09:32:03 +03:00

Owner

Originally created by @Gnbrkm41 on GitHub (Nov 8, 2020).
Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/757

I have a 4K (3840*2160) display @ 100% scaling and a 1080p display @ 100% scaling. The second, smaller display is set as the primary display.

When I use the new capture experience (the one that has a separate outline for the capture region), the capture region appears in the primary (1080p60 @ 100%) monitor and I cannot seem to move it over to the bigger display. The control window moves over just fine; it's only the outline that cannot be moved across.

The ScreenToGif version I'm using is 2.27.3, on Windows 10 Pro (ko-KR, x64) Insiders Preview (Dev channel) Build 20251.

Originally created by @Gnbrkm41 on GitHub (Nov 8, 2020). Original GitHub issue: https://github.com/NickeManarin/ScreenToGif/issues/757 I have a 4K (3840*2160) display @ 100% scaling and a 1080p display @ 100% scaling. The second, smaller display is set as the primary display. When I use the new capture experience (the one that has a separate outline for the capture region), the capture region appears in the primary (1080p60 @ 100%) monitor and I cannot seem to move it over to the bigger display. The control window moves over just fine; it's only the outline that cannot be moved across. The ScreenToGif version I'm using is 2.27.3, on Windows 10 Pro (ko-KR, x64) Insiders Preview (Dev channel) Build 20251.

kerem commented

2026-02-26 09:32:04 +03:00

Author

Owner

@NickeManarin commented on GitHub (Nov 8, 2020):

That was on purpose. I had to fix a small bug which makes hard to detect when the monitor selection changes during drag.

You can move the selection by pressing the "Select area" again.

@NickeManarin commented on GitHub (Nov 8, 2020): That was on purpose. I had to fix a small bug which makes hard to detect when the monitor selection changes during drag. You can move the selection by pressing the "Select area" again.

kerem commented

2026-02-26 09:32:04 +03:00

Author

Owner

@IllusionMH commented on GitHub (Jan 12, 2021):

Also just encountered this behavior and it wasn't obvious for me why I can move it to another screen. Glad that old experience is still available because it was my workaround.

Maybe it is possible to detect that mouse moved 100+px to another screen and show notification that user should create new area on that screen if they want to record it?

a bit offtopic: Are there plans to enable Area capture across multiple monitors in new recorder experience? Haven't found existing issue so should I create new issue or don't bother if not planned at all?
Couple of times it was useful to show how window is resized improperly and affected second screen, but not something that highly used.

@IllusionMH commented on GitHub (Jan 12, 2021): Also just encountered this behavior and it wasn't obvious for me why I can move it to another screen. Glad that old experience is still available because it was my workaround. Maybe it is possible to detect that mouse moved 100+px to another screen and show notification that user should create new area on that screen if they want to record it? a bit offtopic: Are there plans to enable Area capture across multiple monitors in new recorder experience? Haven't found existing issue so should I create new issue or don't bother if not planned at all? Couple of times it was useful to show how window is resized improperly and affected second screen, but not something that highly used.

kerem commented

2026-02-26 09:32:04 +03:00

Author

Owner

@NickeManarin commented on GitHub (Jan 12, 2021):

The issue happens when working with multi-dpi set of screens. It's finick to detect exactly the position of capture window because when changing from 100% to 200% the sizing calculations must change too (and I need to detect which monitor the window is currently using).

Maybe if I look again with a clear mind, I'll be able to fix it without issues.

Right now, I don't have plans in supporting cross-screen selection, due to issues regarding multi-dpi too.
The old UI has this feature because it does not have that selection mechanism. ;/

@NickeManarin commented on GitHub (Jan 12, 2021): The issue happens when working with multi-dpi set of screens. It's finick to detect exactly the position of capture window because when changing from 100% to 200% the sizing calculations must change too (and I need to detect which monitor the window is currently using). Maybe if I look again with a clear mind, I'll be able to fix it without issues. Right now, I don't have plans in supporting cross-screen selection, due to issues regarding multi-dpi too. The old UI has this feature because it does not have that selection mechanism. ;/