Improve fixing process in the Validation Results window

[Olivier-JOURDAN]

When you update the DQMH version, you can have hundreds of failures to fix in your projects (not because everything is broken but just because, for example, a new feature requires updating a VI).

A fixer is available most of the time, and you just have to click the button to make the code change.

For me, the UX issue is that after you hit the fix button, you need to select the next failure with your mouse and then click on the fix button. I'm not too fond of this kind of mouse gymnastics.

My proposition: If the fix is successful, the next failure could be selected automatically.

The fixing process would be significantly improved.

[Darren]

If a fixer runs successfully, we could add a checkmark or something next to the item in the main listbox before moving on to the next item, that would be a good way to visualize that the fixer actually did something.

[Taggart]

Why not a fix-all similar issues button?

Often many of them are exactly the same issue, just applied to several modules or events. Then I have to click through each one seperately.

This would be a low priority for me, because how often do you actually end up upgrading (that's when most of the issues are found)? So clicking through each one is annoying and a slight waste of time, but in the grand scheme of things it's not that much time lost or annoyance.

[Olivier-JOURDAN]

Actually, I have two projects with 40+ modules I've been working on during the last two years. Each DQMH upgrade gives me around 150 fixes to process. So it takes around 300 mouse clicks at two different positions on the screen. Not exactly the best developer experience 😅

I'd love it if we could improve the process with just a little effort.

[Ozfarmboy]

Also, it would be nice to have a column in the listbox to show fixed status.  ie. if you have fixed an issue, then it will show up as fixed in the list.

[joerg.hampel]

Yes please!

I would even go one step further and allow to "Fix all failures of same type in one go". There is no benefit in clicking the Fix button again and again for the same type of error - we're not learning anything new from it.

[joerg.hampel]

We'd really love to see this feature make it into DQMH 7, but it has low priority.