summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRĂ©mi Verschelde <remi@verschelde.fr>2021-10-09 13:40:43 +0200
committerGitHub <noreply@github.com>2021-10-09 13:40:43 +0200
commit096941e629ea1ce7d22a7f6dcd985e5a74cc6ae2 (patch)
treec28d7983bddec2af1dacbc61eea7efceb3c43f2d
parentb22664e160ae28a67dce2cbf3279523cadf74b61 (diff)
parent735618b39e223226c6ea1374e8b1df263d58a0c3 (diff)
Merge pull request #53592 from Calinou/doc-timer-wait-time-fix-typo
-rw-r--r--doc/classes/Timer.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/classes/Timer.xml b/doc/classes/Timer.xml
index fde887dd87..f360099f2b 100644
--- a/doc/classes/Timer.xml
+++ b/doc/classes/Timer.xml
@@ -52,7 +52,7 @@
</member>
<member name="wait_time" type="float" setter="set_wait_time" getter="get_wait_time" default="1.0">
The wait time in seconds.
- [b]Note:[/b] Timers can only emit once per rendered frame at most (or once per physics frame if [member process_callback] is [constant TIMER_PROCESS_PHYSICS). This means very low wait times (lower than 0.05 seconds) will behave in significantly different ways depending on the rendered framerate. For very low wait times, it is recommended to use a process loop in a script instead of using a Timer node.
+ [b]Note:[/b] Timers can only emit once per rendered frame at most (or once per physics frame if [member process_callback] is [constant TIMER_PROCESS_PHYSICS]). This means very low wait times (lower than 0.05 seconds) will behave in significantly different ways depending on the rendered framerate. For very low wait times, it is recommended to use a process loop in a script instead of using a Timer node.
</member>
</members>
<signals>