LabVIEW Idea Exchange

About LabVIEW Idea Exchange

Have a LabVIEW Idea?

  1. Browse by label or search in the LabVIEW Idea Exchange to see if your idea has previously been submitted. If your idea exists be sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea to the LabVIEW Idea Exchange. Be sure to submit a separate post for each idea.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see in a future version of LabVIEW!
cancel
Showing results for 
Search instead for 
Did you mean: 
Yamaeda

Reentrancy icon

Status: New

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.

Reentrancy.png

G# - Award winning reference based OOP for LV, for free! ADDQ VIPM Now on GitHub
"Only dead fish swim downstream" - "My life for Kudos!" - "Dumb people repeat old mistakes - smart ones create new ones."
Certified-LabVIEW-Developer
5 Comments
thols
Active Participant

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?).

Certified LabVIEW Architect
fabric
Active Participant

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...

--
Chris Virgona
wiebe@CARYA
Proven Zealot

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

 

Sort of a show buffer allocations for icons.

thols
Active Participant

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.

Certified LabVIEW Architect
crossrulz
Knight of NI

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


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5