Miroirs/Gtk4-tutorial
1
0
Fork 0
mirror of https://github.com/ToshioCP/Gtk4-tutorial.git synced 2025-01-12 20:03:28 +01:00
Code Issues Projects Releases Packages Wiki Activity Actions

Bug fixed.

Browse source
This commit is contained in:
Toshio Sekiya 2021-06-13 21:47:46 +09:00
parent d7b56d066c
commit 148b5ae68b
2 changed files with 18 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
gfm/sec3.md
View file

@ -105,7 +105,7 @@ A child object inherits signals, functions, properties and so on from its parent
So, Gtkapplication also has the "activate" signal. So, Gtkapplication also has the "activate" signal.
Now we can solve the problem in `pr1.c`. Now we can solve the problem in `pr1.c`.
We need to connect the activate signal to a handler. We need to connect the "activate" signal to a handler.
We use a function `g_signal_connect` which connects a signal to a handler. We use a function `g_signal_connect` which connects a signal to a handler.
~~~C ~~~C
@ -140,10 +140,10 @@ The function `g_signal_connect` has four arguments.
4. Data to pass to the handler. If no data is necessary, NULL should be given. 4. Data to pass to the handler. If no data is necessary, NULL should be given.
You can find the description of each signal in API reference. You can find the description of each signal in API reference.
For example, "activate" signal is in GApplication section in [GIO API reference[(https://developer.gnome.org/gio/stable/GApplication.html#GApplication-activate). For example, "activate" signal is in GApplication section in [GIO API reference](https://developer.gnome.org/gio/stable/GApplication.html#GApplication-activate).
The handler function is described in it. The handler function is described in it.
In addition, `g_signal_connect` is described in [GObject API reference[(https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-signal-connect). In addition, `g_signal_connect` is described in [GObject API reference](https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-signal-connect).
API reference is very important. API reference is very important.
You should see and understand it to write Gtk applications. You should see and understand it to write Gtk applications.
They are located in ['GNOME Developer Center'](https://developer.gnome.org/). They are located in ['GNOME Developer Center'](https://developer.gnome.org/).
@ -202,11 +202,19 @@ What we need to do is:
2. Connect it to GtkApplication. 2. Connect it to GtkApplication.
3. Show the window. 3. Show the window.
Now rewrite the function `add_activate`. Now rewrite the function `app_activate`.
#### Create a GtkWindow #### Create a GtkWindow
~~~C ~~~C
1 static void
2 app_activate (GApplication *app, gpointer user_data) {
3 GtkWidget *win;
4
5 win = gtk_window_new ();
6 gtk_window_set_application (GTK_WINDOW (win), GTK_APPLICATION (app));
7 gtk_widget_show (win);
8 }
~~~ ~~~
Widget is an abstract concept that includes all the GUI interfaces such as windows, dialogs, buttons, multi-line text, containers and so on. Widget is an abstract concept that includes all the GUI interfaces such as windows, dialogs, buttons, multi-line text, containers and so on.
@ -266,7 +274,7 @@ As it destroys itself, the GtkWindow is also destroyed.
The function `gtk_widget_show` is used to show the window. The function `gtk_widget_show` is used to show the window.
Gtk4 changed the default widget visibility to on, so every widget doesn't need this function to show itself. Gtk4 changes the default widget visibility to on, so every widget doesn't need this function to show itself.
But, there's an exception. But, there's an exception.
Top window (this term will be explained later) isn't visible when it is created. Top window (this term will be explained later) isn't visible when it is created.
So you need to use the function above to show the window. So you need to use the function above to show the window.

10
src/sec3.src.md
View file

@ -91,7 +91,7 @@ A child object inherits signals, functions, properties and so on from its parent
So, Gtkapplication also has the "activate" signal. So, Gtkapplication also has the "activate" signal.
Now we can solve the problem in `pr1.c`. Now we can solve the problem in `pr1.c`.
We need to connect the activate signal to a handler. We need to connect the "activate" signal to a handler.
We use a function `g_signal_connect` which connects a signal to a handler. We use a function `g_signal_connect` which connects a signal to a handler.
@@@include @@@include
@ -108,10 +108,10 @@ The function `g_signal_connect` has four arguments.
4. Data to pass to the handler. If no data is necessary, NULL should be given. 4. Data to pass to the handler. If no data is necessary, NULL should be given.
You can find the description of each signal in API reference. You can find the description of each signal in API reference.
For example, "activate" signal is in GApplication section in [GIO API reference[(https://developer.gnome.org/gio/stable/GApplication.html#GApplication-activate). For example, "activate" signal is in GApplication section in [GIO API reference](https://developer.gnome.org/gio/stable/GApplication.html#GApplication-activate).
The handler function is described in it. The handler function is described in it.
In addition, `g_signal_connect` is described in [GObject API reference[(https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-signal-connect). In addition, `g_signal_connect` is described in [GObject API reference](https://developer.gnome.org/gobject/stable/gobject-Signals.html#g-signal-connect).
API reference is very important. API reference is very important.
You should see and understand it to write Gtk applications. You should see and understand it to write Gtk applications.
They are located in ['GNOME Developer Center'](https://developer.gnome.org/). They are located in ['GNOME Developer Center'](https://developer.gnome.org/).
@ -170,7 +170,7 @@ What we need to do is:
2. Connect it to GtkApplication. 2. Connect it to GtkApplication.
3. Show the window. 3. Show the window.
Now rewrite the function `add_activate`. Now rewrite the function `app_activate`.
#### Create a GtkWindow #### Create a GtkWindow
@ -235,7 +235,7 @@ As it destroys itself, the GtkWindow is also destroyed.
The function `gtk_widget_show` is used to show the window. The function `gtk_widget_show` is used to show the window.
Gtk4 changed the default widget visibility to on, so every widget doesn't need this function to show itself. Gtk4 changes the default widget visibility to on, so every widget doesn't need this function to show itself.
But, there's an exception. But, there's an exception.
Top window (this term will be explained later) isn't visible when it is created. Top window (this term will be explained later) isn't visible when it is created.
So you need to use the function above to show the window. So you need to use the function above to show the window.