diff --git a/docs/sec3.html b/docs/sec3.html index 028fdf9..a6b229b 100644 --- a/docs/sec3.html +++ b/docs/sec3.html @@ -209,9 +209,10 @@ explain that to you first.
A signal is emitted when something happens. For example, a window is created, a window is destroyed and so on. The signal “activate” is emitted when the application is activated. (Activated is a bit different -from started, but you can think of them both as almost the same so far.) If the -signal is connected to a function, which is called a signal handler or -simply handler, then the function is invoked when the signal emits.
+from started, but you can think of them both as almost the same so far.) +If the signal is connected to a function, which is called a signal +handler or simply handler, then the function is invoked when the signal +emits.The flow is like this:
It works, but isn’t usually used. Instead, GTK_WINDOW
macro is used.
(win) GTK_WINDOW
The macro is recommended because it does not only cast the pointer but it also checks -the type.
+The macro is recommended because it does not only cast the pointer +but it also checks the type.
The function gtk_window_set_application
is used to
diff --git a/gfm/sec3.md b/gfm/sec3.md
index 6c7f88d..5450e15 100644
--- a/gfm/sec3.md
+++ b/gfm/sec3.md
@@ -114,7 +114,7 @@ So, I will explain that to you first.
A signal is emitted when something happens.
For example, a window is created, a window is destroyed and so on.
The signal "activate" is emitted when the application is activated.
-(Activated is a bit different from started, but you can think the both are almost same so far.)
+(Activated is a bit different from started, but you can think of them both as almost the same so far.)
If the signal is connected to a function, which is called a signal handler or
simply handler, then the function is invoked when the signal emits.
@@ -204,7 +204,7 @@ The parameters are:
- self is an instance to which the signal belongs.
- user\_data is a data defined in the fourth argument of the `g_signal_connect` function.
-If it is NULL, then you can ignore and left out the second parameter.
+If it is NULL, then you can ignore and leave out the second parameter.
API reference manual is very important.
You should see and understand it.
@@ -314,7 +314,7 @@ Instead, `GTK_WINDOW` macro is used.
GTK_WINDOW (win)
~~~
-The macro is recommended because it does not only cast but also check the type.
+The macro is recommended because it does not only cast the pointer but it also checks the type.
#### Connect it to GtkApplication.
diff --git a/gfm/sec4.md b/gfm/sec4.md
index 1b8e3ca..d6a9da1 100644
--- a/gfm/sec4.md
+++ b/gfm/sec4.md
@@ -352,7 +352,7 @@ Then, these two buttons are appended to the box.
10 }
~~~
-The function `gtk_button_get_lable` returns a text from the label.
+The function `gtk_button_get_label` returns a text from the label.
The string is owned by the button and you can't modify or free it.
The `const` qualifier is necessary for the string `s`.
If you change the string, your compiler will give you a waring.
@@ -361,7 +361,7 @@ You always need to be careful with the const qualifier when you see the GTK 4 AP
![Screenshot of the box](../image/screenshot_lb4.png)
-The handler corresponds to `btn1` toggles its label.
-The handler corresponds to `btn2` destroys the top-level window and the application quits.
+The handler corresponding to `btn1` toggles its label.
+The handler corresponding to `btn2` destroys the top-level window and the application quits.
Up: [README.md](../README.md), Prev: [Section 3](sec3.md), Next: [Section 5](sec5.md)
diff --git a/src/sec3.src.md b/src/sec3.src.md
index 5a747ce..090bc7f 100644
--- a/src/sec3.src.md
+++ b/src/sec3.src.md
@@ -100,7 +100,7 @@ So, I will explain that to you first.
A signal is emitted when something happens.
For example, a window is created, a window is destroyed and so on.
The signal "activate" is emitted when the application is activated.
-(Activated is a bit different from started, but you can think the both are almost same so far.)
+(Activated is a bit different from started, but you can think of them both as almost the same so far.)
If the signal is connected to a function, which is called a signal handler or
simply handler, then the function is invoked when the signal emits.
@@ -172,7 +172,7 @@ The parameters are:
- self is an instance to which the signal belongs.
- user\_data is a data defined in the fourth argument of the `g_signal_connect` function.
-If it is NULL, then you can ignore and left out the second parameter.
+If it is NULL, then you can ignore and leave out the second parameter.
API reference manual is very important.
You should see and understand it.
@@ -275,7 +275,7 @@ Instead, `GTK_WINDOW` macro is used.
GTK_WINDOW (win)
~~~
-The macro is recommended because it does not only cast but also check the type.
+The macro is recommended because it does not only cast the pointer but it also checks the type.
#### Connect it to GtkApplication.
diff --git a/src/sec4.src.md b/src/sec4.src.md
index 33ee2f8..5111e96 100644
--- a/src/sec4.src.md
+++ b/src/sec4.src.md
@@ -162,7 +162,7 @@ Then, these two buttons are appended to the box.
misc/lb4.c click1.cb
@@@
-The function `gtk_button_get_lable` returns a text from the label.
+The function `gtk_button_get_label` returns a text from the label.
The string is owned by the button and you can't modify or free it.
The `const` qualifier is necessary for the string `s`.
If you change the string, your compiler will give you a waring.
@@ -171,5 +171,5 @@ You always need to be careful with the const qualifier when you see the GTK 4 AP
![Screenshot of the box](../image/screenshot_lb4.png){width=6.3cm height=5.325cm}
-The handler corresponds to `btn1` toggles its label.
-The handler corresponds to `btn2` destroys the top-level window and the application quits.
+The handler corresponding to `btn1` toggles its label.
+The handler corresponding to `btn2` destroys the top-level window and the application quits.