Refresh Data tab automatically when mods toggle

OrganizerCore::modStatusChanged updates the DirectoryStructure in
place (enabling/disabling origins) but never fires
directoryStructureReady, which is the only signal MainWindow used to
drive DataTab::updateTree. Result: after enabling or disabling a mod
the Data tab kept showing the old virtual tree until the user hit
Refresh manually.

Connect ModList::modStatesChanged directly to DataTab::updateTree so
the file tree re-queries the structure as soon as the toggle lands.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

1 files changed, 7 insertions, 0 deletions

diff --git a/src/src/mainwindow.cpp b/src/src/mainwindow.cpp
index e148c24..1ef6fe1 100644
--- a/src/src/mainwindow.cpp
+++ b/src/src/mainwindow.cpp
@@ -397,6 +397,13 @@ MainWindow::MainWindow(Settings& settings, OrganizerCore& organizerCore,
 

   connect(&m_OrganizerCore, &OrganizerCore::directoryStructureReady, this,

           &MainWindow::onDirectoryStructureChanged);

+

+  // OrganizerCore::modStatusChanged updates the DirectoryStructure in place

+  // but never emits directoryStructureReady, so without this the Data tab

+  // stays stale until the user clicks Refresh. Route the ModList signal to

+  // DataTab::updateTree directly.

+  connect(m_OrganizerCore.modList(), &ModList::modStatesChanged, this,

+          [this] { m_DataTab->updateTree(); });

   connect(m_OrganizerCore.directoryRefresher(),

           SIGNAL(progress(const DirectoryRefreshProgress*)), this,

           SLOT(refresherProgress(const DirectoryRefreshProgress*)));