Browsing Spanish translation

3.

The screen function should have parameters corresponding to the scope variables it expects, and it should ignore extra keyword arguments. (That is, it should have `**kwargs` at the end of its parameter list.) It is then expected to call the UI functions to add displayables to the screen.The screen function is called whenever an interaction starts or restarts.

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.

5.

Here's an example python screen:

6.

Screen Functions

7.

The following functions support the definition, display, and hiding of screens.

8.

The programmatic equivalent of the show screen statement.

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.

10.

Keyword arguments not beginning with _ are passed to the scope of the screen.

11.

If the keyword argument `_with_none` is false, "with None" is not run at the end of end of the interaction.

12.

Defines a screen with `name`, which should be a string.