Skip to content

Commit f5de8dd

Browse files
author
Mike Barkmin
committed
document stage.display
1 parent a07fda4 commit f5de8dd

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

README.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -90,6 +90,8 @@ also display the text for a certain amount of milliseconds like so: `stage.displ
9090
| `stage.removeSprites(MySprite.class)` | Removes all sprites of class MySprite |
9191
| `stage.getSprites()` | Returns a list of all sprites |
9292
| `stage.getSprites(MySprite.class)` | Returns a list of all sprites of class MySprite |
93+
| `stage.display(String text)` | Displays a text at the bottom of the stage |
94+
| `stage.display(String text, int millis)` | Displays a text at the bottom of the stage for a given amount of milliseconds |
9395

9496
#### Sound
9597

@@ -406,7 +408,7 @@ This happens when the frame rate drops. This can lead to an unwanted rendering
406408
order. For example the pattern which was tried to achieve in the example
407409
[TimedDot](#TimeDot) should look like this:
408410

409-
Lila, Lila, Green, Lila, Lila, Green, Clear.
411+
Lila, Lila, Green, Lila, Lila, Green, Clear.
410412

411413
Especially at the beginning of the sketch the frame rate increases slowly to
412414
the desired one. Therefore, there are some missing frames in the beginning and

0 commit comments

Comments
 (0)