GNOME Bugzilla – Bug 556007
GtkWindow.Fullscreen() does not work correctly with multiscreen on OSX
Last modified: 2018-04-14 23:59:07 UTC
Please describe the problem: The GtkWindow.Fullscreen() method does not work as expected under OSX. With a dual monitors setup, when a window on the secondary monitor is made fullscreen it pops up on the primary monitor. This is different than the behaviour on Linux and Windows. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
Created attachment 261226 [details] [review] Patch for 2.24.22 that fixes the issue The attached patch fixes the issue in 2.24.22 Tested in a macbook running OSX Mavericks with a secondary monitor attached.
Review of attachment 261226 [details] [review]: Looks very plausible. Please fix this in both gtk 2.24 and master
I'm sorry but I don't have a development environment for master on OSX right now although looking to the code in master it seems that same issue is there. Please feel free to handle the provided patch in the way that you'll consider most appropriate as I won't be able to spend time for this issue in short.
Created attachment 263023 [details] [review] Patch that fixes the issue The previous provided patch wasn't completely correct as it only worked as expected when secondary screen was at right. So here there's a new patch that works with all screen arrangements.
Tested in Gtk2; this almost works. The only problem is that when the window is unfullscreened it goes to the origin (upper left corner of the leftmost monitor) rather than back to where it started.
This patch isn't perfect, but since it is a lot better than what the current code does, are there any reasons not to merge it?
Instead of full-screening on the wrong monitor, it restores to the wrong monitor when it coming out of full-screen. How is that any better than the current code?
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new