GTK+ 1.2 Tutorial
Prev | Chapter 7. Adjustments | Next

# Adjustment Internals

Ok, you say, that's nice, but what if I want to create my own handlers to respond when the user adjusts a range widget or a spin button, and how do I get at the value of the adjustment in these handlers? To answer these questions and more, let's start by taking a look at `struct _GtkAdjustment` itself:

    struct _GtkAdjustment
    {
      GtkData data;

      gfloat lower;
      gfloat upper;
      gfloat value;
      gfloat step_increment;
      gfloat page_increment;
      gfloat page_size;
    };

The first thing you should know is that there aren't any handy-dandy macros or accessor functions for getting the `value` out of an Adjustment, so you'll have to (horror of horrors) do it like a real C programmer. Don't worry - the `GTK_ADJUSTMENT (Object)` macro does run-time type checking (as do all the GTK type-casting macros, actually).

Since, when you set the `value` of an adjustment, you generally want the change to be reflected by every widget that uses this adjustment, GTK provides this convenience function to do this:

    void gtk_adjustment_set_value( GtkAdjustment *adjustment,
                                   gfloat         value );

As mentioned earlier, Adjustment is a subclass of Object just like all the various widgets, and thus it is able to emit signals. This is, of course, why updates happen automagically when you share an adjustment object between a scrollbar and another adjustable widget; all adjustable widgets connect signal handlers to their adjustment's `value_changed` signal, as can your program. Here's the definition of this signal in `struct _GtkAdjustmentClass`:

      void (* value_changed) (GtkAdjustment *adjustment);

The various widgets that use the Adjustment object will emit this signal on an adjustment whenever they change its value. This happens both when user input causes the slider to move on a range widget, as well as when the program explicitly changes the value with `gtk_adjustment_set_value()`. So, for example, if you have a scale widget, and you want to change the rotation of a picture whenever its value changes, you would create a callback like this:

    void cb_rotate_picture (GtkAdjustment *adj, GtkWidget *picture)
    {
      set_picture_rotation (picture, adj->value);
    ...

and connect it to the scale widget's adjustment like this:

    gtk_signal_connect (GTK_OBJECT (adj), "value_changed",
    	            GTK_SIGNAL_FUNC (cb_rotate_picture), picture);

What about when a widget reconfigures the `upper` or `lower` fields of its adjustment, such as when a user adds more text to a text widget? In this case, it emits the `changed` signal, which looks like this:

      void (* changed) (GtkAdjustment *adjustment);

Range widgets typically connect a handler to this signal, which changes their appearance to reflect the change - for example, the size of the slider in a scrollbar will grow or shrink in inverse proportion to the difference between the `lower` and `upper` values of its adjustment.

You probably won't ever need to attach a handler to this signal, unless you're writing a new type of range widget. However, if you change any of the values in a Adjustment directly, you should emit this signal on it to reconfigure whatever widgets are using it, like this:

    gtk_signal_emit_by_name (GTK_OBJECT (adjustment), "changed");

Now go forth and adjust!

Prev | Home | Next
Using Adjustments the Easy Way | Up | Range Widgets