|
|
16.
|
|
|
Init Python Statement
|
|
|
|
|
Init Python Statement
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:83
|
|
|
17.
|
|
|
The ``init python`` statement runs python code at initialization time, before the game loads. Among other things, this code can be used to define classes and functions, or to initialize styles, config variables, or persistent data. ::
|
|
|
|
|
The ``init python`` statement runs python code at initialization time, before the game loads. Among other things, this code can be used to define classes and functions, or to initialise styles, config variables, or persistent data. ::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:85
|
|
|
18.
|
|
|
A priority number can be placed between ``init`` and ``python``. When a priority is not given, 0 is used. Init statements are run in priority order, from lowest to highest. Init statements of the same priority are run in unicode order by filename, and then from top to bottom within a file.
|
|
|
|
|
A priority number can be placed between ``init`` and ``python``. When a priority is not given, 0 is used. Init statements are run in priority order, from lowest to highest. Init statements of the same priority are run in unicode order by filename, and then from top to bottom within a file.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:105
|
|
|
19.
|
|
|
To avoid conflict with Ren'Py, creators should use priorities in the range -999 to 999. Priorities of less than 0 are generally used for libraries and to set up themes. Normal init code should have a priority of 0 or higher.
|
|
|
|
|
To avoid conflict with Ren'Py, creators should use priorities in the range -999 to 999. Priorities of less than 0 are generally used for libraries and to set up themes. Normal init code should have a priority of 0 or higher.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:110
|
|
|
20.
|
|
|
Init python statements also take the ``hide`` or ``in`` clauses.
|
|
|
|
|
Init python statements also take the ``hide`` or ``in`` clauses.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:115
|
|
|
21.
|
|
|
Variables that have their value set in an init python block are not saved, loaded, and do not participate in rollback, unless the object the variable refers to is changed.
|
|
|
|
|
Variables that have their value set in an init python block are not saved, loaded, and do not participate in rollback, unless the object the variable refers to is changed.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:117
|
|
|
22.
|
|
|
Define Statement
|
|
|
|
|
Define Statement
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:125
|
|
|
23.
|
|
|
The define statement sets a single variable in the default store to a value at init time. For example::
|
|
|
|
|
The define statement sets a single variable in the default store to a value at init time. For example::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:127
|
|
|
24.
|
|
|
is equivalent to::
|
|
|
|
|
is equivalent to::
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:132
|
|
|
25.
|
|
|
One advantage of using the define statement is that it records the filename and line number at which the assignment occured, and makes that available to the navigation feature of the launcher.
|
|
|
|
|
One advantage of using the define statement is that it records the filename and line number at which the assignment occured, and makes that available to the navigation feature of the launcher.
|
|
Translated and reviewed by
Stephan Woidowski
|
|
|
|
Located in
../../source/python.rst:137
|
