We should probably make this a requirement in the future -- it doesn't cost us much to save signal IDs, and allows a lot of extensions to be more flexible.
On Fri, May 17, 2013 at 8:33 PM, Amy <mathematical.cof...@gmail.com> wrote: > Why can't gnome-shell classes all store the IDs of the signals they > connect to, just like extensions are required to :( > > It is so annoying when you can't update your extension because a > gnome-shell class is doing something that an extension would get flat-out > rejected for (i.e., not storing signal connection IDs and disconnecting > when appropriate) :( > > Thanks for clarifying - I will try work out how to make a patch (I've been > told before; just need to review the notes) and submit a patch/bug report > when done. > > > On 17 May 2013 22:43, Florian Müllner <fmuell...@gnome.org> wrote: > >> On Fri, May 17, 2013 at 2:36 PM, Amy <mathematical.cof...@gmail.com> >> wrote: >> > I'm trying to replace the thumbnails box (Main.overview._thumbnailsBox) >> with >> > my own. >> > >> > However, the thumbnails box connects to a few Main.overview signals >> (like >> > showing/hidden) and even though I destroy the thumbnails box's actor, >> the >> > thumbnails box still appears to respond to the signals (causing all >> sorts of >> > segfaults due to the actor being destroyed...) >> >> As the actor is not supposed to be destroyed normally, it's perfectly >> possible that we miss disconnecting the signals. Please don't try to >> workaround this, but file a bug against gnome-shell (of course >> including a patch yourself would be very welcome!) >> >> Thanks, >> Florian >> > > > _______________________________________________ > gnome-shell-list mailing list > gnome-shell-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gnome-shell-list > > -- Jasper
_______________________________________________ gnome-shell-list mailing list gnome-shell-list@gnome.org https://mail.gnome.org/mailman/listinfo/gnome-shell-list
