LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
crelf

Putting a disable structure around a typedef front panel node on the block diagram shouldn't require the typedef to be loaded

Status: Declined
Adding this functionality would break any objects outside of the disabled structure (e.g. property nodes, LabVIEW class, ActiveX, XControls) that were tied to that control reference.

Scenario: I have a section of code that has missing subVIs and controls (they're typedefs), and I want to disable it.  I put a diagram disable structure around the code, and it means that the missing VIs are okay, but LabVIEW still requires the typedef'd controls to be loaded <- this causes a broken arrow, even through the only broken code is within the diagram disable structure.

 

Fix: If the only reference to a typedef control is within the disabled case of a diagram disabled structure, then it should be ignored (and therefore should have to be loaded).





Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
15 Comments
G-Money
NI Employee (retired)
Status changed to: Declined
Adding this functionality would break any objects outside of the disabled structure (e.g. property nodes, LabVIEW class, ActiveX, XControls) that were tied to that control reference.
AristosQueue (NI)
NI Employee (retired)

> Thinking about this a little more: I'm not sure I want the property nodes outside of the

> disable structure breaking.  I mean, maybe I do if it's a typedef, but not if it's a normal

> control.  Also, I agree that I want to do nothing if the terminal is on the conpane, but maybe

> we can use the same argument to do nothing if the terminal has property nodes.

 

So what I'm hearing is this:

 

  1. If all uses of the control are inside a disabled structure (including the FP terminal, all staticallly bound property/invoke nodes and local variables), then the control effectively vanishes from the panel and all behaviors at run time.
  2. If any use of the control is not inside a disabled structure, the control remains in play.
  3. This means that if the control is linked to a typedef, the typedef is loaded if any use of the control is not disabled, but if all uses of the control are disabled then the typedef is not loaded (and, therefore, if the typedef is missing, the VI is not broken).
  4. The use of "typedef" in #3 applies equally to references to LVClasses, XControls, Active X classes and anything else that may in the future be added that a control references.

 

Yes?

AristosQueue (NI)
NI Employee (retired)

This idea, as written, has been declined... if you'd like to repost what we've discussed as a new idea, go for it.

crelf
Trusted Enthusiast

Yes - I like your description.  I'll repost with more clarity.





Copyright © 2004-2024 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 4.0 License.
crelf
Trusted Enthusiast