|
|
@@ -175,8 +175,9 @@ struct ImGuiViewport; // A Platform Window (always only one in 'ma
|
|
|
// Enumerations
|
|
|
// - We don't use strongly typed enums much because they add constraints (can't extend in private code, can't store typed in bit fields, extra casting on iteration)
|
|
|
// - Tip: Use your programming IDE navigation facilities on the names in the _central column_ below to find the actual flags/enum lists!
|
|
|
-// In Visual Studio IDE: CTRL+comma ("Edit.GoToAll") can follow symbols in comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
-// With Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols in comments.
|
|
|
+// - In Visual Studio: CTRL+comma ("Edit.GoToAll") can follow symbols inside comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
+// - In Visual Studio w/ Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols inside comments.
|
|
|
+// - In Visual Studio Code: CTRL+click can follow symbols inside comments.
|
|
|
enum ImGuiKey : int; // -> enum ImGuiKey // Enum: A key identifier (ImGuiKey_XXX or ImGuiMod_XXX value)
|
|
|
enum ImGuiMouseSource : int; // -> enum ImGuiMouseSource // Enum; A mouse input source identifier (Mouse, TouchScreen, Pen)
|
|
|
typedef int ImGuiCol; // -> enum ImGuiCol_ // Enum: A color identifier for styling
|
|
|
@@ -191,8 +192,9 @@ typedef int ImGuiTableBgTarget; // -> enum ImGuiTableBgTarget_ // Enum: A
|
|
|
|
|
|
// Flags (declared as int to allow using as flags without overhead, and to not pollute the top of this file)
|
|
|
// - Tip: Use your programming IDE navigation facilities on the names in the _central column_ below to find the actual flags/enum lists!
|
|
|
-// In Visual Studio IDE: CTRL+comma ("Edit.GoToAll") can follow symbols in comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
-// With Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols in comments.
|
|
|
+// - In Visual Studio: CTRL+comma ("Edit.GoToAll") can follow symbols inside comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
+// - In Visual Studio w/ Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols inside comments.
|
|
|
+// - In Visual Studio Code: CTRL+click can follow symbols inside comments.
|
|
|
typedef int ImDrawFlags; // -> enum ImDrawFlags_ // Flags: for ImDrawList functions
|
|
|
typedef int ImDrawListFlags; // -> enum ImDrawListFlags_ // Flags: for ImDrawList instance
|
|
|
typedef int ImFontAtlasFlags; // -> enum ImFontAtlasFlags_ // Flags: for ImFontAtlas build
|
|
|
@@ -1547,8 +1549,9 @@ enum ImGuiCol_
|
|
|
// - The enum only refers to fields of ImGuiStyle which makes sense to be pushed/popped inside UI code.
|
|
|
// During initialization or between frames, feel free to just poke into ImGuiStyle directly.
|
|
|
// - Tip: Use your programming IDE navigation facilities on the names in the _second column_ below to find the actual members and their description.
|
|
|
-// In Visual Studio IDE: CTRL+comma ("Edit.GoToAll") can follow symbols in comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
-// With Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols in comments.
|
|
|
+// - In Visual Studio: CTRL+comma ("Edit.GoToAll") can follow symbols inside comments, whereas CTRL+F12 ("Edit.GoToImplementation") cannot.
|
|
|
+// - In Visual Studio w/ Visual Assist installed: ALT+G ("VAssistX.GoToImplementation") can also follow symbols inside comments.
|
|
|
+// - In Visual Studio Code: CTRL+click can follow symbols inside comments.
|
|
|
// - When changing this enum, you need to update the associated internal table GStyleVarInfo[] accordingly. This is where we link enum values to members offset/type.
|
|
|
enum ImGuiStyleVar_
|
|
|
{
|
|
|
@@ -2045,6 +2048,9 @@ struct ImGuiStyle
|
|
|
//-----------------------------------------------------------------------------
|
|
|
// Communicate most settings and inputs/outputs to Dear ImGui using this structure.
|
|
|
// Access via ImGui::GetIO(). Read 'Programmer guide' section in .cpp file for general usage.
|
|
|
+// It is generally expected that:
|
|
|
+// - initialization: backends and user code writes to ImGuiIO.
|
|
|
+// - main loop: backends writes to ImGuiIO, user code and imgui code reads from ImGuiIO.
|
|
|
//-----------------------------------------------------------------------------
|
|
|
|
|
|
// [Internal] Storage used by IsKeyDown(), IsKeyPressed() etc functions.
|
ocornut