[Spectacle] [Bug 361053] New: Center “click anywhere” message on screen instead of entire virtual desktop

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361053

Bug ID: 361053
   Summary: Center “click anywhere” message on screen instead of
entire virtual desktop
   Product: Spectacle
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: lach...@hong-mailing.de

Currently, the usage hint in the cropper window is centered in the window
instead of the currently active screen. This should be changed so it only
appears on the active screen and does not span multiple physical displays.

Reproducible: Always

Steps to Reproduce:
1. Use the “rectangular region” capture mode on a system with a virtual desktop
spanning multiple physical displays

Actual Results:  
Message is centered on the virtual desktop, potentially spanning multiple
physical displays.

Expected Results:  
Message is centered on the physical display that corresponds to the active
screen.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361048

--- Comment #8 from Martin Herkt  ---
Yup, fixed. Nice bonus would be to center the “click anywhere” message on the
active screen instead of the entire window.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361048

--- Comment #4 from Martin Herkt  ---
Created attachment 98116
  --> https://bugs.kde.org/attachment.cgi?id=98116=edit
Patch to fix editor pixmap scaling

Almost.
Works with this patch.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Spectacle] [Bug 361036] No support for 30bpp X11 display

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361036

--- Comment #8 from Martin Herkt  ---
Yes, it is. At least I get correct colors now :)
Now if it could save at higher bit depth as well, that would be the icing on
the cake.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Spectacle] [Bug 361048] QML-based cropper does not support virtual desktops spanning multiple screens

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361048

--- Comment #2 from Martin Herkt  ---
Same behavior with KWin.

-- 
You are receiving this mail because:
You are watching all bug changes.


[Spectacle] [Bug 361048] New: QML-based cropper does not support virtual desktops spanning multiple screens

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361048

Bug ID: 361048
   Summary: QML-based cropper does not support virtual desktops
spanning multiple screens
   Product: Spectacle
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: lach...@hong-mailing.de

The QML-based cropper (in git master) currently fullscreens only on a single
display instead of spanning the entire virtual desktop. This is a regression.

Reproducible: Always

Steps to Reproduce:
1. Use “rectangular region” capture mode

Actual Results:  
Cropper displays only on one screen, virtual desktop screenshot is downscaled
to fit. Will save the downscaled region.

Expected Results:  
Cropper window spans entire virtual desktop.

Using i3, not KWin. I don’t think it matters, though.
Displays set up like this:
1920x1080 | 1920x1080 (primary)

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 361036] No support for 30bpp X11 display

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361036

--- Comment #5 from Martin Herkt  ---
Awesome. Poke me if you need me to test patches. I’m lachs0r @ freenode.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 361036] No support for 30bpp X11 display

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361036

--- Comment #3 from Martin Herkt  ---
Whew, no idea if that helps, but I’ve attached xdpyinfo output.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Spectacle] [Bug 361036] No support for 30bpp X11 display

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361036

--- Comment #2 from Martin Herkt  ---
Created attachment 98112
  --> https://bugs.kde.org/attachment.cgi?id=98112=edit
xdpyinfo output

-- 
You are receiving this mail because:
You are watching all bug changes.


[Spectacle] [Bug 361036] New: No support for 30bpp X11 display

2016-03-27 Thread Martin Herkt via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=361036

Bug ID: 361036
   Summary: No support for 30bpp X11 display
   Product: Spectacle
   Version: unspecified
  Platform: openSUSE RPMs
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: General
  Assignee: m...@baloneygeek.com
  Reporter: lach...@hong-mailing.de

Spectacle only supports 24bpp and will not work correctly with a 30bpp X11
display. It loses a few bits, resulting in wrong colors.

Reproducible: Always

Steps to Reproduce:
1. Set the display depth to 30 bpp in your Xorg configuration. E.g. NVIDIA
drivers support this; recommended to use 364.12 (beta as of writing) or newer
as that fixes a number of issues related to full 30bpp support.
2. Run Spectacle and take a screenshot

Actual Results:  
24bpp Screenshot with mangled colors

Expected Results:  
30bpp Screenshot with correct colors (converted to 24bpp or 48bpp if the file
format does not support it)

-- 
You are receiving this mail because:
You are watching all bug changes.