<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken" href="https://bugzilla.gnome.org/show_bug.cgi?id=759626#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Clipboard (copy-and-paste) Wayland→Wayland or Wayland→X11 from closed applications is broken" href="https://bugzilla.gnome.org/show_bug.cgi?id=759626">bug 759626</a> from <a href="page.cgi?id=describeuser.html&login=jadahl%40gmail.com" title="Jonas Ådahl <jadahl@gmail.com>"> Jonas Ådahl</a> <pre>(In reply to Matthias Clasen from <a href="show_bug.cgi?id=759626#c5">comment #5</a>) > (In reply to Michael Catanzaro from <a href="show_bug.cgi?id=759626#c4">comment #4</a>) > > (In reply to Jonas Ådahl from <a href="show_bug.cgi?id=759626#c3">comment #3</a>) > > > Why would there be a need for a new request? Is it for making the client > > > control what selections would be more "persistent" than others or something? > > > Otherwise, it should work already, the way same clipboard.c in weston works. > > > > Oooh, didn't know about this. > > > > Yeah, it's clearly not necessary if we store selection data automatically... > > my mind jumped to it because it's required in ICCM. So we can avoid this > > complexity. > > > > The original purpose of the separate store request was to avoid unnecessary > > clipboard IPC overhead, but it's surely not relevant in 2016. > > We will want an explicit Store for the same reasons it is necessary in X: > You don't want a clipboard manager eagerly collecting megabytes of data > because you happened to hit Ctrl-A in a big spreadsheet. FWIW, one would have to press Ctrl-A then Ctrl-C to actually set the selection (selection here is the Wayland protocol term, not the user interface term). So when would one do a wl_data_device.set_selection() but not a wp_clipboard_manager.store()?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>