<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#c8">Comment # 8</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=mcatanzaro%40gnome.org" title="Michael Catanzaro <mcatanzaro@gnome.org>"> Michael Catanzaro</a> <pre>(In reply to Jonas Ådahl from <a href="show_bug.cgi?id=759626#c7">comment #7</a>) > So when would one do a wl_data_device.set_selection() but not a > wp_clipboard_manager.store()? The clipboard manager only ever needs data if the original client is going to quit or crash. If we do not tolerate data loss when the client crashes, then I suppose we always have to do wp_clipboard_manager.store() and it serves no useful purpose. I think it's reasonable to tolerate clipboard data loss if the application crashes (i.e. if the application is broken). Then GTK+ need only use wp_clipboard_manager.store() when it's quitting (and would hang around long enough to finish that operation after hiding its window). That way we don't wind up doing extra IPC except when really needed.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>