Re: signal functions in a package module file

[Kevin Ryde <user42 zip com au>]

muppet <scott asofyet org> writes:
> But, there's less chance of messing up and letting
> the window be destroyed, so that's a good thing.

Yes, less chance of getting it wrong would be the advantage ...

> > What about adding new constants DO_PROPAGATE and DO_NOT_PROPAGATE to
> > Glib, though?
>
> They are not glib constants --- they would be part of gtk+, to
> complement the semantics of GtkWidget event functions, which use
> _gtk_boolean_handled_accumulator().

Yep.  Constants would make the intention clearer.  Maybe a couple for
the glib idle/timeout sources too, as they're kinda the opposite way
around: event signals return true to "stop", but source handlers return
true to "continue" (being called).

Are there other callbacks yet another way around though?  Signal
GSignalEmissionHook is true for "continue", so it's ok.


-- 
Walk without rhythm and it won't attract the worm.