<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GdkSelection does not support arbitrary named clipboards/selections on wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=770333#c12">Comment # 12</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GdkSelection does not support arbitrary named clipboards/selections on wayland" href="https://bugzilla.gnome.org/show_bug.cgi?id=770333">bug 770333</a> from <a href="page.cgi?id=describeuser.html&login=ebassi%40gmail.com" title="Emmanuele Bassi (:ebassi) <ebassi@gmail.com>"> Emmanuele Bassi (:ebassi)</a> <pre>(In reply to Paolo Bacchilega from <a href="show_bug.cgi?id=770333#c11">comment #11</a>) > I had to revert the change because I found out a use case where a different > clipboard is useful, a detailed description is in the commit > df19186483a5e3edf2ff89cfd92c30bf85b9420f That particular use case is supported by not using a GdkSelection to store the list of selected files in the first place. The only reason why you would use a GdkSelection is, on X11, to use the X protocol as a form of IPC between two separate instances of file-roller; since file-roller is a single-instance application, there's no reason to use a GdkSelection to hold some URIs, since there's no IPC taking place. 'Cut'/'Copy'/'Paste' operations should be implemented inside the file-roller application singleton, by storing row references to the GtkTreeView, or by storing a list of URIs. Even if file-roller were to support multiple instances of the application, you should use a better IPC mechanism, like DBus, instead of the X protocol, as it has unknown latencies (which depend on things like your GPU stalling the event queue) and a woefully inadequate type system.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>