As I said earlier, I'm in favor of this, but it needs to consider that experienced users and beginners have different requirements.
In any case, I think this dialog should be more intelligent - It's probably more important to sort warnings by their severity then by number of occurences - warnings like "constant replaced..." (I assume that was what you meant) are lower priority and should probably not pollute this dialog. The others should have a clear and simple explanation of why they are important very easily accessible (quite possibly already visible). I mind less the magnitude of a change and more the actual effect it has.
I don't think it's a major problem if the details are displayed in a separate window, but it might be good if there would be an environment setting which would allow advanced users to get the details view immediately. An alternate implementation would be to have a summary view and a details view in the same window.
(1) Do you typically read this warning dialog in detail? Do you scan over it looking for particular types of warnings?
It depends - I often know when it's coming (eg: I've explicitly moved something on disk, and I know that LabVIEW's going to relink to VIs in a location that it didn't expect them to be in) so I'll have a quick read through and cancel it out. Other times it surprises me with warnings that I didn't expect, so I read it very very carefully
(2) Do you use the "Save to File..." button to export the warnings to a text file for later examination? If so, do you use any automated tools to parse/filter these text files?
Very rarely - only when I'm surprised by something, and there's a lot of info to go through. As someone else already said, it'd be great if the dialog wasn't modal, and I could work on code with it up - or at least have a look at code that it's flagged.
(3) Does this dialog ever appear at times when you really would rather it be suppressed? Is it ever essential to suppress this dialog?
Never - that said, it'd be nice to have categroies of info rather than everything in a big text block, then I can quickly decide what's important and what's not. Maybe like the LabVIEW Options dialog - categories on the left and descriptions with hotlinks to the VIs (or even the components of the VIs) on the right.
Good question, Albert. The distinction between "warnings for loading" and "normal warnings" is admittedly a bit fuzzy, and we don't have any official, consistent terminology to explain it. Here's my attempt...
Albert Geven wrote:
It seems like a good approach, especially that I can get to this warnings later.
How do you differentiate between warnings for loading and the normal warnings (like hidden terminal)
Excellent idea Albert,
Whenever I open a VI posted here in the forum, the first thing I do is check the VI properties to see from what version it came from. This would eliminated that step.
If you want something faster than that, how about writing a simple VI which will go into the tools menu and just return a popup with the version of the VI it's called from?
Alternatively, I'm not sure how Firefox \ IE 7 plugins work, but if you can call an arbitrary executable, you could write a small LV app which will call the Get VI Version method with command line arguments and embed it in the browser. Of course, loading the RTE just for that seems like overkill.