Capture region, on a multiple monitor setup is capturing part of another screen, not only the one in context

First of all, thanks for a great app that have been following me for years.

I also just wanted to +1 this. The thread is a few years old now, but I’m also experiencing this on the same software version. Is it really true that the current version 1.2.10.6 was released in 2017? Pretty solid work if releases aren’t necessary more often (That’s a compliment, if it didn’t show ). Also, do you want bug reports here in Jira and/or in Github Issues?

I have three monitors, left-center-right, all at 100% DPI:

• L: Laptop at 1920x1080

• C: Dell at 2560x1440 (Windows Main monitor)

• R: Dell at 1440x2560 (vertical)

I experience much the same as when using the “Capture region screenshot” in that if my mouse cursor is at the middle monitor, all is good, but if I have my mouse cursor on either left or right monitor, it seems like in either case, it takes a preliminary screenshot of the left monitor (to use for dragging a rectangle) and it also sort of swaps the resolutions on the two. If the mouse is on the left monitor, I get a preliminary screenshot of the left monitor, but pushed down with black on top, as if the resolution was in vertical mode and the laptop monitor was way heigher than it is. If the mouse is on the right monitor, I get a preliminary screenshot still of the left monitor, but shown on the right (vertical) monitor with black both on top and bottom. See screenshots below.

I do believe I have had this kind of issue before (years back), and somehow the monitor placement setup in Windows (the above screenshot) the displays were just slightly off-placed. I guess at that time I had two like monitors in horizontal mode next to each other, but in Windows the one was slightly higher set than the other. Setting them on the same height solved the issue. But in my current setup, my laptop is on a riser and the vertical obviously is also not the same height placement. But maybe this info can get you going? I have tried moving both monitors a bit but to no avail.

I do have PowerToys installed and using the FancyZones tool - and also having “Open new window on mouse cursor monitor” (or what that’s name is..) enabled. I could do some tinkering with this, although I quite like the current setup of PowerToys/FancyZones.

If you need some kind of logs, please let me know where to get it and you’ll get it straight away.

My hotkey setup

Region screen capture of the left screen by using hotkey with the mouse on the left monitor

Region screen capture of the left screen by using tray icon menu (taskbar is on the center screen). Works fine.

Region screen capture of the right screen by using hotkey with the mouse on the right monitor. Notice the crosshair is way off-screen but only a little two low. I guess the same as the bottom transparency artifact mentioned below?.

Region screen capture of the right screen by using tray icon menu (taskbar is on the center screen). Works fine.

Full screen capture of the left screen by using hotkey with the mouse on the left monitor - notice artifacts on the bottom

Full screen capture of the left screen by tray icon menu (taskbar is on the center screen) - no artifacts

Window screen capture of the left screen by using hotkey with the mouse on the left - notice artifacts on the bottom

Window screen capture of the left screen by tray icon menu (taskbar is on the center screen) - no artifacts

So it happens only when using keyboard hotkeys and only when mouse cursor is on left or right monitor, not the main monitor. I just tried moving my taskbar to the left and right monitor and using the tray menus, so the mouse cursor is on the left or right monitor while using the tray menus, but this is failing the same way. I was actually thinking this would have had some effect but no.

My best guess as a fellow coder (without having looked at your code repo), is that the height position is somehow based upon the main monitor even though mouse cursor is on either left or right monitor, topped up with some swapping between left and right? The right region is just slightly wrong (except getting the preliminary screenshot from the wrong monitor), and the left region is also off but probably at the same height as the top black bar on the right preliminary screenshot. And you do something different when using keyboard hotkeys than using tray menus.

I hope my description here isn’t too confusing :-)

Best regards,

SvendK

Just to chime in, I have the same problem (I think). I have a pretty irregular monitor formation of 3 screens, 2x1080p screens and 1x5120x1440p screen, all at different DPI settings.

The Ultrawide is in the middle with one screen in landscape directly above it, centred. The other screen is to the left, in portrait:

When I press print screen, greenshot’s capture window opens up completely off-centre and with a different screen showing. I don’t know how I can take a screenshot of what I’m seeing, but it looks a lot like what Paul has posted here.
The capture window itself is off-centre and it’s inconsistent, different depending on where my mouse cursor is when I press the button.

I’ve tried both the latest stable and the latest unstable version of Greenshot.

What’s notable is that it sometimes works correctly actually, but I can’t spot a pattern to it.

Oh, and 1.2.10.6

I’ve got a multi-monitor setup at work suffering from this for a couple of months. Crosshairs start on my side monitor, with the display enlarged / shifted, but my workaround was to move my content to the other, unaffected monitor and hit PrtScn again so a second pair of crosshairs would jump over and allow me to get my screenshot.

Now it’s happening on a single monitor setup at home, so I can’t do that workaround. While triggering the shortcut will give you a second crosshair that aligns with the mouse, it looks like at least one monitor always has a screen shifting problem. Here’s a photo of the monitor during the problem, and some screens following the second triggering:

Thanks Robin, yes updated and yes a work around for now