ImGuiWindow is mostly a dumb struct. It merely has a constructor and a few helper methods

Draw callbacks

Intentionally empty. Used as an identifier for rendering loop to call its code. Simpler to implement this way.

[experimental] Borrowed from GLFW's function updateFramebufferTransparency() in src/win32_window.c (the Dwm* functions are Vista era functions but we

Helper function to enable DPI awareness without setting up a manifest

FIXME: Positive values only.

Constructors, destructor

Consider using _stricmp/_strnicmp under Windows or strcasecmp/strncasecmp. We don't actually use either ImStricmp/ImStrnicmp in the codebase any more.

Functions - If GetPixels() functions asserts while being called by your render loop, it could be caused by calling ImFontAtlas::Clear() instead of Cle

- ImageButton() adds style.FramePadding*2.0f to provided size. This is in order to facilitate fitting an image in a button. - ImageButton() draws a ba

- Read about ImTextureID/ImTextureRef here: https://github.com/ocornut/imgui/wiki/Image-Loading-and-Displaying-Examples - 'uv0' and 'uv1' are texture

Public API

Note: p_data, p_step, p_step_fast are _pointers_ to a memory address holding the data. For an Input widget, p_step and p_step_fast are optional. Read

If you want to use InputText() with std::string or any custom dynamic string type, use the wrapper in misc/cpp/imgui_stdlib.h/.cpp!

As InputText() retain textual data and we currently provide a path for user to not retain it (via local variables) we need some form of hook to reappl

Edit a string of text - buf_size account for the zero-terminator, so a buf_size of 6 can hold "Hello" but not "Hello!". This is so we can easily call

Tip: use ImGui::PushID()/PopID() to push indices or pointers in the ID stack. Then you can keep 'str_id' empty or the same for all your buttons (inste