Reentrancy icon

[Yamaeda]

So, i just found a bit of code with a parallell loop, containing a non reentrant vi, making it moot. I guess we've all been there, and those things can be hard to spot.

Suggestion: Mark reentrancy with an automatic small corner icon similar type def, e.g. in different colors depending on if it's Shared or preallocated.

[thols]

No, there are many other properties that one may find important enough to think it has to be a glyph for it on the icon. What makes reentrancy special? Maybe better to find a way to easily debug that scenario (like looking through each VIs setting manually, which doesn't take so much time).

Maybe you can identify a set of rules that applies to your application(s) for when a VI should be reentrant and make a test for that to catch it (VI analyzer?).

[fabric]

I've always wanted a better indicator of reentrancy (and a few other properties), but I also understand the perils of adding more and more glyphs to the diagram.

The context help seems like the best contender as a suitable place to display such information. See related discussion here: https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Show-Reentrancy-in-Context-Help/idi-p/2723353?profile...

[wiebe@CARYA]

There could be a global setting dialog to turn on\off different icon overlays.

Sort of a show buffer allocations for icons.

[thols]

Almost duplicate of https://forums.ni.com/t5/LabVIEW-Idea-Exchange/reentrant-VI-indicator/idc-p/3130825/highlight/true#M....

Similar to https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Icon-editor-could-suggest-glyphs-to-include-based-on-...

The idea of temporarily displaying these kind of things like for showing buffer allocations is an interesting idea. Another way is to globally select what layers/types of glyphs/properties to view. A bit like defining a view in a CAD application (house architect analogy here): Do we want a plumbing/electrical view, do we want to see the furniture or not, and so on. Even defining view-presets for specific purposes, like debugging reentrancy issues e.g.

[crossrulz]

VI Analyzer has a "Reentrancy" test that would have found this issue.