Slideshow: With Twinview enabled and two displays, Shotwell doesn't always use the display it was opened on.
Submitted by cli..@..ba.org
Link to original bug (#717539)
Description
---- Reported by clinton@yorba.org 2011-05-05 14:51:00 -0700 ----
Original Redmine bug id: 3579
Original URL: http://redmine.yorba.org/issues/3579
Searchable id: yorba-bug-3579
Original author: Clinton Rogers
Original description:
To reproduce:
On a computer with Nvidia video hardware, enable TwinView.
From the Nvidia control panel, set the displays to different resolutions.
Launch Shotwell and place its window on the smaller of the two displays.
Launch the slideshow and observe the results.
Notice that, regardless of where Shotwell's window is when the slideshow is started, the slideshow appears on the larger of the two displays.
Originally reported via Launchpad: https://bugs.launchpad.net/ubuntu/source/shotwell/bug/778100
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:39:00 -0700 ----
History
Comment 1
Updated by Valentín Barros over 2 years ago
The problem was in the call to set_default_size in FullscreenWindow's constructor.
Passing the arguments get_screen().get_width/height() to that method works well in a single monitor configuration, but when we have two or more in a extended-monitor configuration, get_screen().get_width/height() refers to the width/height of the entire screen (i.e. the sum of the monitors' width/height, depending of the configuration I mean, if you are using them one above another or one aside another). With this, we are telling window system that the window is more higher/wider than one monitor, so when we call fullscreen() the result could be a bit odd as another example additionally to the reported one, in my configuration if I have the main window in my second monitor and I start the slideshow, I get it in the same monitor but in the workspace right to the one where the main window was.
I've simply changed get_screen().get_width/height() to monitor.width/height and all works fine for me using an extended-monitor configuration with an ATI graphics card.
So, I attach a patch.
Comment 2
Updated by Adam Dingle over 2 years ago
- Target version set to 0.10
Comment 3
Updated by Lucas Beeler over 2 years ago
- Resolution set to fixed
- % Done changed from 0 to 100
Closed in b6357e07.
Comment 4
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:52 UTC ---
This bug was previously known as bug 3579 at http://redmine.yorba.org/show_bug.cgi?id=3579 Imported an attachment (id=262023)
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.10
Resolution: RESOLVED FIXED