mirror of https://github.com/kivy/kivy.git
fixed line numbers in : docs/guide/firstwidget.html (6_button.py)
This commit is contained in:
parent
7cf8c4952e
commit
36f303868c
|
@ -286,27 +286,27 @@ Here's what happens:
|
||||||
|
|
||||||
* Line 4: We added an import statement to be able to use the
|
* Line 4: We added an import statement to be able to use the
|
||||||
:class:`~kivy.uix.button.Button` class.
|
:class:`~kivy.uix.button.Button` class.
|
||||||
* Line 26: We create a dummy ``Widget()`` object as a parent for both
|
* Line 25: We create a dummy ``Widget()`` object as a parent for both
|
||||||
our painting widget and the button we're about to add. This is just
|
our painting widget and the button we're about to add. This is just
|
||||||
a poor-man's approach to setting up a widget tree hierarchy. We
|
a poor-man's approach to setting up a widget tree hierarchy. We
|
||||||
could just as well use a layout or do some other fancy stuff.
|
could just as well use a layout or do some other fancy stuff.
|
||||||
Again: This widget does absolutely nothing except holding the two
|
Again: This widget does absolutely nothing except holding the two
|
||||||
widgets we will now add to it as children.
|
widgets we will now add to it as children.
|
||||||
* Line 27: We create our ``MyPaintWidget()`` as usual, only this time
|
* Line 26: We create our ``MyPaintWidget()`` as usual, only this time
|
||||||
we don't return it directly but bind it to a variable name.
|
we don't return it directly but bind it to a variable name.
|
||||||
* Line 28: We create a button widget. It will have a label on it that
|
* Line 27: We create a button widget. It will have a label on it that
|
||||||
displays the text 'Clear'.
|
displays the text 'Clear'.
|
||||||
* Line 29 & 30: We set up the widget hierarchy by making both the
|
* Line 28 & 29: We set up the widget hierarchy by making both the
|
||||||
painter and the clear button children of the dummy parent widget.
|
painter and the clear button children of the dummy parent widget.
|
||||||
That means painter and button are now siblings in the usual computer
|
That means painter and button are now siblings in the usual computer
|
||||||
science tree terminology.
|
science tree terminology.
|
||||||
* Lines 32 & 33: Up to now, the button did nothing. It was there,
|
* Lines 31 & 32: Up to now, the button did nothing. It was there,
|
||||||
visible, and you could press it, but nothing would happen.
|
visible, and you could press it, but nothing would happen.
|
||||||
We change that here: We create a small throw-away function that is
|
We change that here: We create a small throw-away function that is
|
||||||
going to be our callback function which is called when the button is
|
going to be our callback function which is called when the button is
|
||||||
pressed. The function just clears the painter's canvas' contents,
|
pressed. The function just clears the painter's canvas' contents,
|
||||||
making it black again.
|
making it black again.
|
||||||
* Line 34: We bind the button's on_release event (which is fired when
|
* Line 33: We bind the button's on_release event (which is fired when
|
||||||
the button is pressed and then released) to the callback we just
|
the button is pressed and then released) to the callback we just
|
||||||
defined.
|
defined.
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue