[Wayland-bugs] [Bug 746723] testxinerama fails under wayland

[gtk+ (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=746723

--- Comment #4 from Jonas Ådahl <jadahl at gmail.com> ---
(In reply to Matthias Clasen from comment #3)
> (In reply to Jonas Ådahl from comment #2)
> 
> > Whats the usual reasons for needing to do gtk_window_move() (including to
> > certain outputs), and are there maybe other ways we can expose such
> > functionality?
> 
> Use cases that could be relevant:
> 
> - A special purpose application that needs to control on which outputs its
> windows go (think trading desk, 3 monitors...). Sounds like 'special
> compositor' to me

Sounds a bit specialized yes, but I wonder if some kind of "remember my
position" and "restore my position" protocol could kind of solve that. It has
been discussed before, but no one has come up with a good solution to how to do
it so far AFIAK.

> 
> - Click on a link in application A to open a document in another application
> - may want to keep the new window on the same monitor ?

There has been ideas floating around about a startup notification / controlled
positioning kind of protocol that could solve this.

> 
> - Implement a 'open window on other monitor' function inside an app (I think
> we're just debating adding 'move to other monitor' in the shell window menu
> elsewhere).

What would the point of opening the window on some other monitor being?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20150325/b415d24c/attachment.html>