<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: new window momentarily displays on wrong monitor" href="https://bugzilla.gnome.org/show_bug.cgi?id=782183#c11">Comment # 11</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - wayland: new window momentarily displays on wrong monitor" href="https://bugzilla.gnome.org/show_bug.cgi?id=782183">bug 782183</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=782183#c10">comment #10</a>) > > [...] > > First thing I can think of is to move part of the maximize code behind a > MetaWindowClass vfunc, as there are multiple things in > meta_window_maximize() that is X11 only (such as unshading, and this > defer-maximize thing). > > Another idea, is to get rid of that deferred-maximize thing all together. It > seems to originate from 2003 with no explanation as to why, and I don't know > how to trigger it either. When checking how it works with the panel-gtk test > case under X11, window-props.c handles initial maximization in a different > way. Given that meta_window_maximize() seems to be called mostly by > interactive window management operations, the two places I think needs > consideration are: meta_window_apply_session_info() (should probably set the > defer-maximize variables, as done in window-props.c), and > meta_window_x11_client_message(). I am not sure I follow, what is it you call "deferred-maximize", is it maximize_horizontally_after_placement and maximize_vertically_after_placement?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>