From 50cbe82f51eaec12f03fc653da56bb1c424f3a63 Mon Sep 17 00:00:00 2001 From: John Geddes Date: Tue, 7 Nov 2023 03:25:36 -0800 Subject: [PATCH] Corrected a small typo. --- Getting-Started.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Getting-Started.md b/Getting-Started.md index 6f09889..9a74449 100644 --- a/Getting-Started.md +++ b/Getting-Started.md @@ -32,7 +32,7 @@ For various reasons, our examples are very raw: we don't load fancy fonts and ge ## Game Loop? -Dear ImGui comes from a game development background, where applications are expected to updating continuously at interactive framerates (e.g. 60 FPS) and where it is expected that an underlying graphics-heavy application in running and showing behind Dear ImGui. This is how our examples are generally structured. While it is technically possible to lift some of those assumptions when using Dear ImGui (e.g. going idle, using variable frame rates, having no "main viewport"), those uses cases are currently not well supported by default, requires a more intimate understanding of both the system and dear imgui, and are outside the scope of this article. +Dear ImGui comes from a game development background, where applications are expected to updating continuously at interactive framerates (e.g. 60 FPS) and where it is expected that an underlying graphics-heavy application is running and showing behind Dear ImGui. This is how our examples are generally structured. While it is technically possible to lift some of those assumptions when using Dear ImGui (e.g. going idle, using variable frame rates, having no "main viewport"), those uses cases are currently not well supported by default, requires a more intimate understanding of both the system and dear imgui, and are outside the scope of this article. A typical game-like application taking advantage of GPU rendering would run in a loop: ```cpp