Re: [gtk-list] Re: an additional argument flag

[Tim Janik <timj gimp org>]

On 23 Feb 1998, Owen Taylor wrote:

> Kenneth Albanowski <kjahds@kjahds.com> writes:
> 
> > On 22 Feb 1998, Tero Pulkkinen wrote:
> > 
> > > Deriving from widgets is the only thing we need to do with gtk--. No
> > > black magic involved. Deriving from widgets currently requires that
> > > we rewrite all *_new() methods. On some widgets this cut/paste is kinda
> > > large as there is static methods called from *_new() methods :)
> > 
> > Have you found some way of deal with class signals (or whatever you want
> > to call the signal slots that are held in the class object) in a
> > reasonable manner? Then again, C++ isn't an interpreter, so you won't have
> > many of the difficulties I ran into with Perl. 
> 
> I think the difficulty that you are referring to is that you
> want to override the default handlers, but the default handlers
> don't go through the marshalling system.
> 
> I think there is a an easy solution to this:
> 
> Signal handlers are called in the order:
> 
>      default handlers of type RUN_FIRST or RUN_BOTH
> 
>      signals connected normally
> 
>      default handlers of type RUN_AFTER or RUN_BOTH.
                                ^^^^^^^^^
                                that has to be GTK_RUN_LAST
> 
>      signals connect "after"

with one exception, the GtkObject::destroy signal.
you cannot "after" connect to a destroy signal.

> 
> Regards,
>                                         Owen
> 

---
ciaoTJ