Batch ID depends on display type. It is either a build ID (when combinding by build type) or batch timestamp otherwise.

FIXME-TESTS: Mostly the same code as ScrollbarEx()

Helper functions

Setup inputs in the tested Dear ImGui context. Essentially we override the work of the backend here.

Create test context (not bound to any dear imgui context yet)

Export using settings stored in ImGuiTestEngineIO This is called by ImGuiTestEngine_CrashHandler().

This is mostly a copy of ImGuiTestEngine_PrintResultSummary with few additions.

FIXME: Work toward simplifying this function?

Supported values for ImGuiTestOpFlags: - ImGuiTestOpFlags_NoError

May want to add support for ImGuiTestOpFlags_NoError if item does not exist?

May want to add support for ImGuiTestOpFlags_NoError if item does not exist?

Important: always call MouseWheelX()/MouseWheelY() with an understand that holding Shift will swap axises. - On Windows/Linux, this swap is done in Im

Simulate a platform window closure.

Tri-state button. Copied and modified ButtonEx().

Helper functions

Sample viewport for an easy location with nothing on it. FIXME-OPT: If ever any problematic: - (1) could iterate g.WindowsFocusOrder[] now that we mad

Supported values for ImGuiTestOpFlags: - ImGuiTestOpFlags_MoveToEdgeL - ImGuiTestOpFlags_MoveToEdgeR - ImGuiTestOpFlags_MoveToEdgeU - ImGuiTestOpFlags

Those strings are used to output easily identifiable markers in compare logs. We only need to support what we use for testing. We can probably grab in

Turn __DATE__ "Jan 10 2019" into "2019-01-10"

Returns a next element of decorated hash path. "//hello/world/child" --> "world/child" "world/child" --> "child" This is a helper for code nee