Visual cues for incompatibility reasons #3271
Merged
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.
Motivation
We continue to get questions about why a mod is shown as incompatible when the user expects it to be compatible. The answer is that there is a conflict or an unsatisfied dependency, but this is generally not obvious.
Changes
Now if a mod is incompatible because of the KSP versions,
<!>
is added to its Versions tab, which shows the range of compatible versions:And if a mod is incompatible because of a conflict or an unsatisfied dependency,
<!>
is added to its Relationships tab, which shows those relationships:Ideally these would have been big red stop sign icons instead, but Mono's
TabControl
does not display icons (it makes room for them if you setTabPage.ImageIndex
orTabPage.ImageKey
, but they're never drawn 🙄).Priorities in choosing these characters: