Bug 372409 - Background for Rectangular Region Interferes with Region Selection
Summary: Background for Rectangular Region Interferes with Region Selection
Status: RESOLVED DUPLICATE of bug 368739
Alias: None
Product: Spectacle
Classification: Applications
Component: General (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-11-13 00:09 UTC by David Rankin
Modified: 2017-10-18 17:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Rankin 2016-11-13 00:09:56 UTC
Version 16.08.3 - Sorry For Any Inconvenience

KDE Frameworks 5.27.0
Qt 5.7.0 (built against 5.7.0)
The xcb windowing system

When capturing a rectangular region Spectacle shades the screen obscuring the details needed to mark the start and end of the desired capture region. Changing the preferences, unselecting [ ] Use light background color, does not remove the shading, but makes the shading dark making it virtually impossible to see the screen at all on laptops.

There should be a way to completely disable this shading entirely as it makes it more difficult in many cases to select the desired rectangular region. ksnapshot worked perfectly without any shading allowing you to accurately capture the region of interest. The shading makes it impossible to determine where to start/stop a region when attempting to avoid parts of gradients, etc... forcing yet another import into gimp to clean up what should have been a simple screen grab.

I would include a screenshot showing the problem, but since spectacle can't even run a multiple instance -- that is impossible too. (frustrating, when ksnapshot had none of these issues)
Comment 1 Peter Wu 2016-11-14 11:02:13 UTC
Would it help if the dark area becomes lighter and less opaque?
Comment 2 Nate Graham 2017-10-18 17:26:32 UTC

*** This bug has been marked as a duplicate of bug 368739 ***