kaka.farm

commit d8ecebeab7034659eb31de2a8310e5c0c2fa0312
parent 4a0791da47fc65cbd73d3f3fe1b58d74add5a527
Author: Yuval Langer <yuval.langer@gmail.com>
Date:   Sat, 29 Jan 2022 04:18:05 +0200

Fix list numbering.

Diffstat:
M
content/2022-01-29-python-gtk-scale-value-changed-event-handler.md
 | 
6
+++---

1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/content/2022-01-29-python-gtk-scale-value-changed-event-handler.md b/content/2022-01-29-python-gtk-scale-value-changed-event-handler.md
@@ -9,7 +9,7 @@ In Glade:
 2. In the `Signals -> GtkRange -> value-changed` line change the `Handler`
     field to something sensible like `on_foo_scale_value_changed`. That will
     be the name of the handler.
-2. Make a new Adjustment in:
+3. Make a new Adjustment in:
 
     ```
     General ->
@@ -19,10 +19,10 @@ In Glade:
     New
     ```
 
-3. Rename the adjustment to something sensible like `foo_adjustment` and set
+4. Rename the adjustment to something sensible like `foo_adjustment` and set
     the `Value`, `Minimum Value`, `Maximum Value`, etc. Those are kind of self
     explanatory…
-4. In Python, your handler will be called with a single argument - the signal
+5. In Python, your handler will be called with a single argument - the signal
     emitting object, which is the GtkScale object itself. It has a method,
     `get_value()`, used to get its current value: