GtkSignalRunType

Warning GtkSignalRunType is deprecated and should not be used in newly-written code. These configure the signal's emission. They control whether the signal can be emitted recursively on an object and whether to run the default method before or after the user-defined handlers. GTK_RUN_FIRST Run the default handler before the connected user-defined handlers. GTK_RUN_LAST Run the default handler after the connected user-defined handlers. (Handlers registered as "after" always run after the default handler though) GTK_RUN_BOTH Run the default handler twice, once before the user-defined handlers, and once after. GTK_RUN_NO_RECURSE Whether to prevent a handler or hook from reemitting the signal from within itself. Attempts to emit the signal while it is running will result in the signal emission being restarted once it is done with the current processing. You must be careful to avoid having two handlers endlessly reemitting signals, gtk_signal_n_emissions() can be helpful. GTK_RUN_ACTION The signal is an action you can invoke without any particular setup or cleanup. The signal is treated no differently, but some other code can determine if the signal is appropriate to delegate to user control. For example, key binding sets only allow bindings of ACTION signals to keystrokes. GTK_RUN_NO_HOOKS This prevents the connection of emission hooks to the signal.

Values

ValueMeaning
RUN_FIRSTSignalFlags.RUN_FIRST
RUN_LASTSignalFlags.RUN_LAST
RUN_BOTH(RUN_FIRST | RUN_LAST)
RUN_NO_RECURSESignalFlags.NO_RECURSE
RUN_ACTIONSignalFlags.ACTION
RUN_NO_HOOKSSignalFlags.NO_HOOKS

Meta