From b9cf21733db4db0bbf8990c169fde2dd12bae427 Mon Sep 17 00:00:00 2001
From: ocornut <omar@miracleworld.net>
Date: Thu, 18 Jun 2026 18:06:10 +0200
Subject: [PATCH] Tables: avoid forcing a settings load on count change.
 (#9108)

At this very moment, I don't have a specific need/use for it. Went into this direction with solving the bigger problem, and it seems right but is not hard required right now.
---
 imgui_tables.cpp | 5 ++++-
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/imgui_tables.cpp b/imgui_tables.cpp
index 5a1d86267..e449b7ea3 100644
--- a/imgui_tables.cpp
+++ b/imgui_tables.cpp
@@ -578,7 +578,7 @@ bool    ImGui::BeginTableEx(const char* name, ImGuiID id, int columns_count, ImG
     if (table->RawData == NULL)
     {
         TableBeginInitMemory(table, columns_count);
-        table->IsInitializing = table->IsSettingsRequestLoad = true;
+        table->IsInitializing = true;
     }
     if (table->IsResetAllRequest)
         TableResetSettings(table);
@@ -586,7 +586,10 @@ bool    ImGui::BeginTableEx(const char* name, ImGuiID id, int columns_count, ImG
     {
         // Initialize
         if (is_new_table)
+        {
             table->SettingsOffset = -1;
+            table->IsSettingsRequestLoad = true;
+        }
         table->IsSortSpecsDirty = true;
         table->IsSettingsDirty = true; // Records itself into .ini file even when in default state (#7934)
         table->InstanceInteracted = -1;