mirror of
https://github.com/ocornut/imgui.git
synced 2026-11-06 06:25:54 +01:00
Updated Getting Started (markdown)
parent
ffe7c2e0dd
commit
5f19b30dc8
@ -37,7 +37,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 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 technically possible but 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 update 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 technically possible but 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
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user