Re: Memory leaks

2011-02-09 Thread Tristan Schmelcher
I think it's worth pointing out that these normally harmless leaks would become a problem if gtk was repeatedly loaded and unloaded with dlopen()+dlclose(). Each dlopen() results in a fresh state, so Gtk would allocate new instances of these global structures each time. Not exactly a prominent use

Re: Receiving a callback on GDK window destroy

2010-01-20 Thread Tristan Schmelcher
al_connect(G_OBJECT(gtk_plug_), "delete-event",    G_CALLBACK(gtk_widget_hide_on_delete), NULL); Thanks for the help! On 19 January 2010 20:55, Kevin DeKorte wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On 01/19/10 20:29, Tristan Sc

Re: Receiving a callback on GDK window destroy

2010-01-19 Thread Tristan Schmelcher
Actually, after debugging and looking at the code, it seems that gdk_window_foreign_new() first looks up if there is already a GdkWindow for that XID and re-uses it if so (gdk/x11/gdkwindow-x11.c:1008). So I don't think this approach will work. :( On 19 January 2010 19:09, Tristan Schme

Re: Receiving a callback on GDK window destroy

2010-01-19 Thread Tristan Schmelcher
> Hash: SHA1 > > On 01/15/10 16:51, Tristan Schmelcher wrote: > > Hello, > > > > I'm a novice Gtk app developer writing a plugin for Firefox and I'm > > having trouble getting the callbacks that I need from Gtk/Gdk. The way > > the plugin archi

Receiving a callback on GDK window destroy

2010-01-15 Thread Tristan Schmelcher
Hello, I'm a novice Gtk app developer writing a plugin for Firefox and I'm having trouble getting the callbacks that I need from Gtk/Gdk. The way the plugin architecture works is that Firefox creates a GtkSocket and my plugin gets passed its XID and creates the corresponding GtkPlug (in the same p