You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Presumably that mentioned installed folder doesn't actually exist, right?
So the bug here is that the "browse installed files" button should not be clickable until a Thrive version has been installed.
That can probably be done with a pretty simple check when opening the settings (or when the install location has changed) to see if the target install folder exists or not and set a view model property that disables the button if it doesn't.
hhyyrylainen
changed the title
Installation folder does not exist
Installation folder does not exist error when browse installed button can be pressed
Jan 11, 2023
Presumably that mentioned installed folder doesn't actually exist, right?
Yep
So the bug here is that the "browse installed files" button should not be clickable until a Thrive version has been installed.
I would disagree, the button should be clickable, the folder should be attempted to be created on launch. And warn the user if for whatever reason it can't be created.
That can probably be done with a pretty simple check when opening the settings (or when the install location has changed) to see if the target install folder exists or not
And attempt to create it, if creation fails a flag can be made to warn the user.
the folder should be attempted to be created on launch
I disagree. The launcher is used for example for Steam and itch.io seamless mode. The launcher should not create extraneous folders that may never be required by certain users.
It was even back in v1 that the install folder is only created the first time a Thrive version is attempted to be created.
Describe the bug
During a fresh install, the "Browse Installed Files" button fails to function.
To Reproduce
Expected behavior
Folder opens up with no issue
Screenshots
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: