GObject.SignalFlags
The signal flags are used to specify a signal's behaviour, the overall signal description outlines how especially the RUN flags control the stages of a signal emission.
- SignalFlags.RUN_FIRST
Invoke the object method handler in the first emission stage.
- SignalFlags.RUN_LAST
Invoke the object method handler in the third emission stage.
- SignalFlags.RUN_CLEANUP
Invoke the object method handler in the last emission stage.
- SignalFlags.NO_RECURSE
Signals being emitted for an object while currently being in emission for this very object will not be emitted recursively, but instead cause the first emission to be restarted.
- SignalFlags.DETAILED
This signal supports "::detail" appendices to the signal name upon handler connections and emissions.
- SignalFlags.ACTION
Action signals are signals that may freely be emitted on alive objects from user code via GObject.signal_emit and friends, without the need of being embedded into extra code that performs pre or post emission adjustments on the object. They can also be thought of as object methods which can be called generically by third-party code.
- SignalFlags.NO_HOOKS
No emissions hooks are supported for this signal.
- SignalFlags.MUST_COLLECT
Varargs signal emission will always collect the arguments, even if there are no signal handlers connected. Since 2.30.
- SignalFlags.DEPRECATED
The signal is deprecated and will be removed in a future version. A warning will be generated if it is connected while running with G_ENABLE_DIAGNOSTIC=1. Since 2.32.