GNOME Bugzilla – Bug 692123
Exchanging arbitrary items with the Mac OS X system clipboard
Last modified: 2018-04-15 00:06:23 UTC
Created attachment 233930 [details] [review] Patch to allow quartz application to properly interact with the Mac OS X clipboard The gtk+ quartz backend supports few mimetypes to be exchanged with the system clipboard. This behavior prevents some application (like Inkscape) from fully working with the OSX clipbaord, using any mimetype. Mimetypes are mapped to the correct Uniform Type identifier, on the fly, using MAc oS x convenience functions. It works very weel with Inkscape.
Created attachment 234111 [details] [review] New patch, added management of NULLs
I added management of NULLs, required to handle all Apple Uniform types. Please use the patch labeled "New patch, added management of NULLs" ignore the previous one
Review of attachment 234111 [details] [review]: Thanks for the patch. When you submit patches, please check the "patch" box on the "add an attachment" form. You'll also see an "obsoletes" selection just below it which allows you to easily supersede previous versions. You'll find instructions for creating patches at https://live.gnome.org/GnomeLove/SubmittingPatches. Please use that procedure and resubmit.
Created attachment 234351 [details] [review] Resubmitted patch, formatted with git, as requested
Created attachment 235656 [details] [review] Revised patch Revised patch: "application/x-color" and "text/uri-list" have to be maintained as separate cases, as Mac OS X does not provide correct translation with UIT's
Valerio, would you mind checking the patches in bug 571582 ? I have just merged the bottom 2 of kris' 3 patches upstream, but these were cleanups only. The 3rd patch actually implements selections in GDK properly and kills gtkselection-quartz.c. If would be great if you could test that stuff, apply your changes on top, and comment :)
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla. If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab: https://gitlab.gnome.org/GNOME/gtk/issues/new