https://bugs.kde.org/show_bug.cgi?id=516970
--- Comment #21 from Konstantin <[email protected]> --- > This actually is what Spectacle does. If both screens have the same scale, > there shouldn't be any re-scaling within Spectacle, as far as I can recall. > It's only when there are multiple screen scales that rescaling becomes > inevitable. Yes, I have a different scale on the screens. Maybe it can be done so that the screenshots don't get blurry? After all, the screenshot of the entire screen is clear. I agree that rescaling is unavoidable if the selected rectangle actually spans outputs with different scale factors. But I don't think it should be unavoidable when the rectangular selection is entirely contained within a single output. Could Spectacle detect that case and use the native capture of that output as the source for the final image? The combined/workspace image could still be used for the rectangular-selection UI, but after the selection is confirmed: determine whether the selection is fully contained in one output; use that output's native-resolution screenshot; transform the selection coordinates into that output's native pixel coordinates; crop it directly, without rescaling. Only selections that actually intersect multiple outputs with different scale factors would need the current stitching/rescaling path. In my case, if a Full Screen capture of the 4K@125% output already has perfect native quality, a rectangular selection entirely inside that same output should theoretically be obtainable from exactly those same pixels. -- You are receiving this mail because: You are watching all bug changes.
