Signals

In GTK programming, each object is capsulated. And it is not recommended to use global variables because they tend to make the program complicated. So, we need something to communicate between objects. There are two ways to do so.

Functions. For example, tb = gtk_text_view_get_buffer (tv). The function caller requests tv, which is a GtkTextView object, to give back tb, which is a GtkTextBuffer object connected to tv.
Signals. For example, activate signal on GApplication object. When the application is activated, the signal is emitted. Then the handler, which has been connected to the signal, is invoked.

The caller of the function or the handler connected to the signal is usually outside of the object. One of the difference between these two is that the object is active or passive. In functions the object responds to the caller. In signals the object actively sends a signal to the handler.

GObject signal can be registered, connected and emitted.

A signal is registered with the object type on which it can be emitted. This is done usually when the class is initialized.
It is connected to a handler by g_connect_signal or its family functions.
When it is emmitted, the connected handler is invoked.

Step one and three are done in the object on which the signal is emitted. Step two is usually done outside the objects.

Signal registration

In TfeTextView, two signals are registered.

"change-file" signal. This signal is emitted when tv->file is changed.
"open-response" signal. tfe_text_view_open function is not able to return the status because of using GtkFileChooserDialog. This signal is emitted instead of the return value of the function.

Static variable is used to store the signal ID. If you need to register two or more signals, static array is usually used.

enum {
  CHANGE_FILE,
   OPEN_RESPONSE,
  NUMBER_OF_SIGNALS
};

static guint tfe_text_view_signals[NUMBER_OF_SIGNALS];

Signal registration codes are written in the class initialization function.

 1 static void
 2 tfe_text_view_class_init (TfeTextViewClass *class) {
 3   GObjectClass *object_class = G_OBJECT_CLASS (class);
 4 
 5   object_class->dispose = tfe_text_view_dispose;
 6   tfe_text_view_signals[CHANGE_FILE] = g_signal_newv ("change-file",
 7                                  G_TYPE_FROM_CLASS (class),
 8                                  G_SIGNAL_RUN_LAST | G_SIGNAL_NO_RECURSE | G_SIGNAL_NO_HOOKS,
 9                                  NULL /* closure */,
10                                  NULL /* accumulator */,
11                                  NULL /* accumulator data */,
12                                  NULL /* C marshaller */,
13                                  G_TYPE_NONE /* return_type */,
14                                  0     /* n_params */,
15                                  NULL  /* param_types */);
16   GType param_types[] = {G_TYPE_INT}; 
17   tfe_text_view_signals[OPEN_RESPONSE] = g_signal_newv ("open-response",
18                                  G_TYPE_FROM_CLASS (class),
19                                  G_SIGNAL_RUN_LAST | G_SIGNAL_NO_RECURSE | G_SIGNAL_NO_HOOKS,
20                                  NULL /* closure */,
21                                  NULL /* accumulator */,
22                                  NULL /* accumulator data */,
23                                  NULL /* C marshaller */,
24                                  G_TYPE_NONE /* return_type */,
25                                  1     /* n_params */,
26                                  param_types);
27 }

6-15: Register "change-file"signal. g_signal_newv function is used. This signal has no default handler (object method handler). You usually don't need to set a default handler in final type object. If you need it, put the closure of the handler in line 9.
The return value of g_signal_newv is the signal id. The type of signal id is guint, which is the same as unsigned int. It is used when the signal is emitted.
16-26: Register "open-response" signal. This signal has a parameter.
25: Number of the parameter. "open-response" signal has one parameter.
26: An array of types of parameters. The array param_types is defined in line 16. It has one element, which is G_TYPE_INT. G_TYPE_INT is a type of integer. Such fundamental types are described in GObject API reference.

The handlers are as follows.

void change_file_handler (TfeTextView *tv, gpointer user_data);
void open_response_handler (TfeTextView *tv, guint parameter, gpointer user_data);

Because "change-file" signal doesn't have parameter, the handler's parameter is TfeTextView object and user data.
Because "open-response" signal has one parameter, the handler's parameter is TfeTextView object, the parameter and user data.
tv is the object instance on which the signal is emitted.
user_data comes from the fourth argument of g_signal_connect.
parameter comes from the fourth argument of g_signal_emit.

The parameter is defined in tfetextview.h because it is public.

/* "open-response" signal response */
enum
{
  TFE_OPEN_RESPONSE_SUCCESS,
  TFE_OPEN_RESPONSE_CANCEL,
  TFE_OPEN_RESPONSE_ERROR
};

TFE_OPEN_RESPONSE_SUCCESS is set when tfe_text_view_open successfully has opend a file and loaded it.
TFE_OPEN_RESPONSE_CANCEL is set when the user has canceled to open a file.
TFE_OPEN_RESPONSE_ERROR is set when error has occured.

Signal connection

A signal and a handler are connected by the function g_signal_connect. There are some similar functions like g_signal_connect_after, g_signal_connect_swapped and so on. However, g_signal_connect is the most common function. The signals "change-file" is connected to a callback function file_changed outside of TfeTextView object. In the same way, the signals "open-response" is connected to a callback function open_response outside of TfeTextView object. The functions file_changed and open_response will be explained later.

g_signal_connect (GTK_TEXT_VIEW (tv), "change-file", G_CALLBACK (file_changed), nb);

g_signal_connect (TFE_TEXT_VIEW (tv), "open-response", G_CALLBACK (open_response), nb);

Signal emission

Signals are emitted on the object. The type of the object is the second argument of g_signal_newv. The relationship between the signal and object (type) is made up when the signal is generated.

g_signal_emit is used to emit the signal. The following is extract from tfetexties.c.

g_signal_emit (tv, tfe_text_view_signals[CHANGE_FILE], 0);
g_signal_emit (tv, tfe_text_view_signals[OPEN_RESPONSE], 0, TFE_OPEN_RESPONSE_SUCCESS);
g_signal_emit (tv, tfe_text_view_signals[OPEN_RESPONSE], 0, TFE_OPEN_RESPONSE_CANCEL);
g_signal_emit (tv, tfe_text_view_signals[OPEN_RESPONSE], 0, TFE_OPEN_RESPONSE_ERROR);

The first argument is the object on which the signal is emitted.
The second argument is the signal id.
The third argument is the detail of the signal. "change-file" signal and "open-response" signal doesn't have details and the argument is zero when no details.
"change-file" signal doesn't have parameter, so no fourth parameter.
"open-response" signal has one parameter. The fourth parameter is the parameter.

Up: Readme.md, Prev: Section 10, Next: Section 12

7.4 KiB Raw Blame History

Signals

Signals

Signal registration

Signal connection

Signal emission

7.4 KiB

Raw Blame History