After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 705978 - gtkdnd-quartz.c missing gicon functions
gtkdnd-quartz.c missing gicon functions
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Backend: Quartz
3.6.x
Other Mac OS
: Normal normal
: ---
Assigned To: gtk-quartz maintainers
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-08-14 10:32 UTC by Bruce Mitchener
Modified: 2018-04-15 00:14 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Adds stubs for the gicon functions (1.41 KB, patch)
2013-08-15 19:17 UTC, John Ralls
none Details | Review

Description Bruce Mitchener 2013-08-14 10:32:44 UTC
In Gtk+ 3.2, these functions were added:

 * gtk_drag_source_set_icon_gicon
 * gtk_drag_set_icon_gicon

They are implemented in gtkdnd.c but not in gtkdnd-quartz.c.

I'm writing bindings for GTK+3 for http://opendylan.org/ and we require that all symbols be defined (on OS X at least), so this shows up as a link time error for us.

I'm using Gtk+-3.6.4 via jhbuild, but this omission appears to still be present in the master branch.
Comment 1 John Ralls 2013-08-15 19:17:08 UTC
Created attachment 251765 [details] [review]
Adds stubs for the gicon functions

Try this patch. It's against master, but it should work with 3.6.4.

It just stubs out those two functions. Actually implementing them is a fair amount of work, and there's a pending partial patch to implement GdkSelection (Bug 571582) which we hope will let us remove 
gtkdnd-quartz and gdkclipboard-quartz entirely and use the mainline modules instead. I'd rather put the time into finishing that up.
Comment 2 Matthias Clasen 2018-02-10 05:18:13 UTC
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.
Comment 3 Matthias Clasen 2018-04-15 00:14:40 UTC
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