Additional UI changes to help user confusion and information #2374
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2372
Added a few more features to the UI to help ease support burden.
Added check that the install folder isnt inside the download folder
Removed the overwrite installation checkbox - it didnt save its state anymore as far as I can tell, and clicking it saved you one click by avoiding the "are you sure you want to overwrite?" prompt. - so clicking once to avoid one click isnt much of a good deal, and it caused user confusion as to its actual purpose.
I've added a hard drive space checker to the install and download paths, ( if same drive itll add the required download and install together ), and itll block the install if there isnt enough space
Ive added some red warning text under the file picker textbox, to additionally outline the current blocking error, so user does not need to be told "hover your mouse over warning label" to find out what the current error is.
Ive expanded the error message text for existing files in the chosen install path, to make it clear that if user is updating an existing modlist, then it is fine to continue.
Updated error message text for protected folders to be more clear about what a protected folder means, and what user might need to do to avoid targeting them
Ive added an additional button to the install failure screen, that links to the wabbajack wiki, so users might press it on an install failure and get some self-help
I have more comprehensive plans in this area, but I see this as more pressing in the meantime due to the number of support queries regarding these install blocking errors.
( self-conscious disclaimer - I am obviously still very new to ReactiveUI/WPF, and c# in general , coming from other languages I may not be aware of some common patterns, so apologies for the roughness of this - currently nobody else is stepping up to fix these things in the short-term, so I will, but I will gladly step back if somebody implements these things better )
Pictures here: