|
|
4.
|
|
|
To ensure that this restarting is seamless to the user (and not causing things to reset), it's important that every call to a UI function supply the `id` argument. As a screen is re-created, Ren'Py will update each displayable with the contents of the old displayable with the same id. Ids are generated automatically by the screen language, but when doing things by hand, they must be manually specified.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:20
|
|
|
5.
|
|
|
Here's an example python screen:
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:28
|
|
|
6.
|
|
|
Screen Functions
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:47
|
|
|
7.
|
|
|
The following functions support the definition, display, and hiding of screens.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/screen_python.rst:49
|
|
|
8.
|
|
|
The programmatic equivalent of the show screen statement.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:5
../../source/inc/screens:73
|
|
|
9.
|
|
|
This shows `_screen_name` as a screen, then causes an interaction to occur. The screen is hidden at the end of the interaction, and the result of the interaction is returned.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:7
|
|
|
10.
|
|
|
Keyword arguments not beginning with _ are passed to the scope of the screen.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:11
|
|
|
11.
|
|
|
If the keyword argument `_with_none` is false, "with None" is not run at the end of end of the interaction.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:14
|
|
|
12.
|
|
|
Defines a screen with `name`, which should be a string.
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:19
|
|
|
13.
|
|
|
`function`
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../../source/inc/screens:27
|
