Re: g_signal_handlers_block_by_func
- From: Tristan Van Berkom <tristan van berkom gmail com>
- To: Neil Zanella <nzanella gmail com>
- Cc: GTK List <gtk-list gnome org>
- Subject: Re: g_signal_handlers_block_by_func
- Date: Wed, 8 Dec 2004 17:08:07 -0500
On Wed, 8 Dec 2004 15:00:28 -0700, Neil Zanella <nzanella gmail com> wrote:
> On Mon, 6 Dec 2004 09:08:43 -0500, Tristan Van Berkom
>
>
> <tristan van berkom gmail com> wrote:
> > On Fri, 3 Dec 2004 16:33:27 -0700, Neil Zanella <nzanella gmail com> wrote:
> > > Hello,
> > >
> > > I would like to know whether the function call
> > >
> > > g_signal_handlers_block_by_func
> > >
> > > can be applied to (external) events in the same way as it can be applied
> > > to (internal) Gtk signals so as to temporarily block them and then call
> > [...]
> > The GSignal api works on GSignals, sometimes there is some confusion
> > about events & signals (I think theres something in the reference about that...)
> >
> > Signals on the GtkWidgetClass with the suffix "-event" (like
> > "button-press-event")
> > are events, but that doesn't mean that they are not signals.
> >
> > So the answer is yes and no, if the external event is a signal, you can
> > block it with the GSignal API, otherwise...
>
> So does this mean that unless the signal/event ends with the suffix "-event"
> then I can block it with g_signal_handlers_block_by_func?
No, it means that as long as it is a signal, you can block it ;-)
(ahem, that doesn't mean that it is recomendable to block event type signals)
Cheers,
-Tristan
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]