diff options
| author | AL <26797547+Al12rs@users.noreply.github.com> | 2020-03-30 22:10:15 +0200 |
|---|---|---|
| committer | AL <26797547+Al12rs@users.noreply.github.com> | 2020-03-30 22:10:15 +0200 |
| commit | a4ed20295f87de040e3afd4bc47777ccb6f47a75 (patch) | |
| tree | 6f7ac1aebe704bd57508f8f7af12f26abc78d653 /src/main.cpp | |
| parent | aab5a120ff59ba4d2cc72e1282fd159c1e97ee19 (diff) | |
Fix "Failed to setup data paths" loop by showing the choose instance dialog for next startup.
This could sometimes happen if users changed a drive letter or removed a drive with one of the Mo2 paths on it making Mo2 error on startup. Only fix was to manually edit the modorganizer.ini file or manually deleting the instance. This allows users to create or use other instances even if that particular instance still needs manual fixing.
Diffstat (limited to 'src/main.cpp')
| -rw-r--r-- | src/main.cpp | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/main.cpp b/src/main.cpp index 10887825..ceaa59f2 100644 --- a/src/main.cpp +++ b/src/main.cpp @@ -527,6 +527,7 @@ int runApplication(MOApplication &application, SingleInstance &instance, if (!bootstrap()) { reportError("failed to set up data paths"); + InstanceManager::instance().clearCurrentInstance(); return 1; } @@ -561,6 +562,7 @@ int runApplication(MOApplication &application, SingleInstance &instance, OrganizerCore organizer(settings); if (!organizer.bootstrap()) { reportError("failed to set up data paths"); + InstanceManager::instance().clearCurrentInstance(); return 1; } @@ -951,6 +953,7 @@ int main(int argc, char *argv[]) if (!createAndMakeWritable(AppConfig::logPath())) { reportError("Failed to create log folder"); + InstanceManager::instance().clearCurrentInstance(); return 1; } |
