Untyped pointer to the underlying GtkSpinButton instance.

Typed pointer to the underlying GtkSpinButton instance.

Required Initialiser for types conforming to SpinButtonProtocol

Bind a SpinButtonPropertyName source property to a given target object.

Get the value of a SpinButton property

Set the value of a SpinButton property. Note that this will only have an effect on properties that are writable and not construct-only!

Connect a Swift signal handler to the given, typed SpinButtonSignalName signal

Connect a C signal handler to the given, typed SpinButtonSignalName signal

Emitted to convert the users input into a double value.

The signal handler is expected to use [methodGtk.Editable.get_text] to retrieve the text of the spinbutton and set new_value to the new value.

The default conversion uses g_strtod().

Emitted when the user initiates a value change.

This is a keybinding signal.

Applications should not connect to it, but may emit it with g_signal_emit_by_name() if they need to control the cursor programmatically.

The default bindings for this signal are Up/Down and PageUp/PageDown.

Typed change-value signal for using the connect(signal:) methods

Emitted to tweak the formatting of the value for display.

// show leading zeros
static gboolean
on_output (GtkSpinButton *spin,
           gpointer       data)
{
   GtkAdjustment *adjustment;
   char *text;
   int value;

   adjustment = gtk_spin_button_get_adjustment (spin);
   value = (int)gtk_adjustment_get_value (adjustment);
   text = g_strdup_printf ("`02d`", value);
   gtk_spin_button_set_text (spin, text):
   g_free (text);

   return TRUE;
}

Typed output signal for using the connect(signal:) methods

Emitted when the value is changed.

Also see the [signalGtk.SpinButton::output] signal.

Typed value-changed signal for using the connect(signal:) methods

Emitted right after the spinbutton wraps from its maximum to its minimum value or vice-versa.

Typed wrapped signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::adjustment signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::climb-rate signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::digits signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::numeric signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::snap-to-ticks signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::update-policy signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::value signal for using the connect(signal:) methods

The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.

Note that getting this signal doesn’t itself guarantee that the value of the property has actually changed. When it is emitted is determined by the derived GObject class. If the implementor did not create the property with G_PARAM_EXPLICIT_NOTIFY, then any call to g_object_set_property() results in notify being emitted, even if the new value is the same as the old. If they did pass G_PARAM_EXPLICIT_NOTIFY, then this signal is emitted only when they explicitly call g_object_notify() or g_object_notify_by_pspec(), and common practice is to do that only when the value has actually changed.

This signal is typically used to obtain change notification for a single property, by specifying the property name as a detail in the g_signal_connect() call, like this:

(C Language Example):

g_signal_connect (text_view->buffer, "notify::paste-target-list",
                  G_CALLBACK (gtk_text_view_target_list_notify),
                  text_view)

It is important to note that you must use canonical parameter names as detail strings for the notify signal.

Typed notify::wrap signal for using the connect(signal:) methods

Changes the properties of an existing spin button.

The adjustment, climb rate, and number of decimal places are updated accordingly.

Changes the properties of an existing spin button.

The adjustment, climb rate, and number of decimal places are updated accordingly.

Get the adjustment associated with a GtkSpinButton.

Returns the acceleration rate for repeated changes.

Fetches the precision of spin_button.

Gets the current step and page the increments used by spin_button.

See [methodGtk.SpinButton.set_increments].

Returns whether non-numeric text can be typed into the spin button.

Gets the range allowed for spin_button.

See [methodGtk.SpinButton.set_range].

Returns whether the values are corrected to the nearest step.

Gets the update behavior of a spin button.

See [methodGtk.SpinButton.set_update_policy].

Get the value in the spin_button.

Get the value spin_button represented as an integer.

Returns whether the spin button’s value wraps around to the opposite limit when the upper or lower limit of the range is exceeded.

Replaces the GtkAdjustment associated with spin_button.

Sets the acceleration rate for repeated changes when you hold down a button or key.

Set the precision to be displayed by spin_button.

Up to 20 digit precision is allowed.

Sets the step and page increments for spin_button.

This affects how quickly the value changes when the spin button’s arrows are activated.

Sets the flag that determines if non-numeric text can be typed into the spin button.

Sets the minimum and maximum allowable values for spin_button.

If the current value is outside this range, it will be adjusted to fit within the range, otherwise it will remain unchanged.

Sets the policy as to whether values are corrected to the nearest step increment when a spin button is activated after providing an invalid value.

Sets the update behavior of a spin button.

This determines whether the spin button is always updated or only when a valid value is set.

Sets the value of spin_button.

Sets the flag that determines if a spin button value wraps around to the opposite limit when the upper or lower limit of the range is exceeded.

Increment or decrement a spin button’s value in a specified direction by a specified amount.

Manually force an update of the spin button.

The adjustment that holds the value of the spin button.

Returns the acceleration rate for repeated changes.

The number of decimal places to display.

Whether non-numeric characters should be ignored.

Returns whether the values are corrected to the nearest step.

Gets the update behavior of a spin button.

See [methodGtk.SpinButton.set_update_policy].

The current value.

Get the value spin_button represented as an integer.

Whether a spin button should wrap upon reaching its limits.