Bug 359078 - Mouse cursor with rectangular region misplaced, too large, and wronge graphic
Summary: Mouse cursor with rectangular region misplaced, too large, and wronge graphic
Status: RESOLVED FIXED
Alias: None
Product: Spectacle
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Boudhayan Gupta
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-06 18:48 UTC by Kai Uwe Broulik
Modified: 2016-04-25 17:51 UTC (History)
0 users

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


Attachments
Wrong cursor (108.93 KB, image/jpeg)
2016-02-06 18:49 UTC, Kai Uwe Broulik
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Uwe Broulik 2016-02-06 18:48:49 UTC
When I take a rectangular region screenshot using Meta+Shift+Print the mouse cursor in the screenshot is misplaced, too large, and the graphic is wrong (ie. usually showing either the cross-hair for selecting a region or the hand for moving said selection)

Reproducible: Always

Steps to Reproduce:
1. Use QT_DEVICE_PIXEL_RATIO=2
2. Press Meta+Shift+PrtScr (I think just doing a rectangular selection from the UI should work also)
3. Save screenshot

Actual Results:  
There will be a mouse cursor in the screenshot at a wrong position, it will be too large, and the graphic will be wrong.

Expected Results:  
The cursor will be at the appropriate position in the correct size and using the graphic the cursor would have in the window I snapshotted rather than of the selection window (if that's not possible, just use the default arrow cursor)
Comment 1 Kai Uwe Broulik 2016-02-06 18:49:58 UTC
Created attachment 97056 [details]
Wrong cursor

You can see by the hovered item in the list where the mouse actually was
Comment 2 Boudhayan Gupta 2016-02-06 18:53:59 UTC
Can I sit on this for a while? I want to eventually fix this with a QtQuick-based replacement.
Comment 3 Boudhayan Gupta 2016-04-25 17:51:51 UTC
This is fixed with your patch in 16.04