Re: [gtk-list] Re: GTK_RUN_ACTION flag. What is it?
- From: Tim Janik <timj gtk org>
- To: gtk-list redhat com
- cc: Michael Lausch <mla gams co at>
- Subject: Re: [gtk-list] Re: GTK_RUN_ACTION flag. What is it?
- Date: Sat, 3 Apr 1999 18:56:16 +0200 (CEST)
On 2 Apr 1999, Owen Taylor wrote:
>
> Michael Lausch <mla@gams.co.at> writes:
>
> > What's the meaning of the GTK_RUN_ACTION flag when defining signals?
>
> The flag means that the signal is suitable for being
> used in a binding definition in an RC file.
>
on a more general note, GTK_RUN_ACTION actually means that users are allowed
to emit this signal at any time on the widget via some of the gtk_signal_emit*
variants. GTK_RUN_ACTION signals are guarranteed to not require specific pre
or post emission handling.
as a counterexample, for instance the GtkWidgetClass::map signal would only
be emitted for !MAPPED widgets and requires the widget to be realized before
signal emission, and eventually needs to be accompanied by a subsequent redraw,
thus it could never be emitted directly without the wrapper code from
gtk_widget_map().
the GtkButton::clicked, GtkCList::scroll_vertical or GtkEditable::move_cursor
signals on the other hand don't require extra wrapping code and thus are all of
type GTK_RUN_ACTION, and maybe invoked from user code directly with
gtk_signal_emit() (take care of the required parameter lists) or can be used
for rc-bindings as owen already pointed out.
>
> Regards,
> Owen
---
ciaoTJ
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]