The "change-event" signal is emitted once per change event that
affects this settings object. You should connect to this signal
only if you are interested in viewing groups of changes before they
are split out into multiple emissions of the "changed" signal.
For most use cases it is more appropriate to use the "changed" signal.
In the event that the change event applies to one or more specified
keys, keys will be an array of GQuark of length n_keys. In the
event that the change event applies to the gtk.Settings object as a
whole (ie: potentially every key has been changed) then keys will
be NULL and n_keys will be 0.
The default handler for this signal invokes the "changed" signal
for each affected key. If any other connected handler returns
TRUE then this default functionality will be suppressed.
The "change-event" signal is emitted once per change event that affects this settings object. You should connect to this signal only if you are interested in viewing groups of changes before they are split out into multiple emissions of the "changed" signal. For most use cases it is more appropriate to use the "changed" signal.
In the event that the change event applies to one or more specified keys, keys will be an array of GQuark of length n_keys. In the event that the change event applies to the gtk.Settings object as a whole (ie: potentially every key has been changed) then keys will be NULL and n_keys will be 0.
The default handler for this signal invokes the "changed" signal for each affected key. If any other connected handler returns TRUE then this default functionality will be suppressed.