Skip to content

Restrict red background highlighting to timestamp conflicts #656

@Infernio

Description

@Infernio

Right now we use it for:

  • Deactivate-tagged plugins that are active.
  • Two plugins that share the same mtime (Last Modified timestamp).

Problems with this:

  1. The first one isn't nearly as bad as the second one - if you're not using a BP, there is no point in ever worrying about it and you might as well just set the color to white in the settings. Plus the BP already gives you a prompt to deactivate all Deactivate-tagged ones. And the Plugin Checker warns too. And we mark the plugin in italics.
  2. The highlighting makes the entry pretty much unreadable, especially if you are visually impaired or colorblind.
  3. The fact that these two problems are the ones that get this highlighting is odd. There are some much more serious issues that WB does not highlight this way (active plugin with missing masters, Skyrim LE BSA on Skyrim SE, etc. - those cause crashes, but we don't do any kind of weird highlight there).

As a result, people keep getting confused by this.

So my proposal is:

  • Remove the highlighting in the first case (redundant as mentioned above, plus makes it harder to figure out at a glance what problems your load order has).
  • Tone down the color in the second case to make it more readable (quick draft below).

image

(lighter color is inactive mtime conflict, darker color is active mtime conflict)

Metadata

Metadata

Assignees

Labels

A-accessibilityArea: Accessibility (improvements for people with disabilities)A-guiArea: GUI (The wx wrapper classes in the gui package)A-usabilityArea: Usability (UX improvements that benefit everyone)C-enhancementCategory: Enhancement, a request to add or enhance a featureM-relnotesMisc: Issue should be listed in the version history for its milestone

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions