Re: gtk_notebook_set_current_page and the switch-page signal

[Tristan Van Berkom <tvb gnome org>]

Francesco Montorsi wrote:
> Hi all,
>
>      I'd like to know how to change the currently selected page in a 
> GtkNotebook *without* generating a switch-page signal.
>
> My switch-page handler in fact performs some code which should be 
> executed only on user-actions, not on selection changes by GTK.

from the docs about "switch-page":
    "Emitted when the user or a function changes the current page"

 a.) "switch-page" maybe isnt exactly where all that logic belongs ?

 b.) maybe your code actually _knows_ that it is in the process of manually
     setting the page of the notebook and should just behave accordingly ?

> PS: is there a convention/rule in GTK+ about signals generated by the 
> user vs signals generated programmatically calling functions?
> I.e. which functions generate events and which not ?

Signals are part of regular program flow, all (or almost all) signals
can be triggered programatically - some are triggered by the object code
that that recieved an event - some signals are triggered by your code
since you called an api from a callback in another signal, this can
and will get very recursive under normal circumstances.

On the other hand, there is a slew of signals on GtkWidgetClass that
are infact "event" aliases delivered from gdk, they all bear the "-event"
suffix and its worth knowing the difference between the two.

Cheers,
                      -Tristan