LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why exactly can't I inline this?

 

Inlining this would open the BD even if password protected.

BDO.png

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 11 of 15
(1,758 Views)

It took several attempts, but I did manage to get a CAR filed for the fact that property nodes accessing class properties are not inlinable despite the fact that the accessor VI behind the PN access was itself inlinable.

 

I was loving life, had some snazzy looking code, finally stopped worrying about creating icons on all my accessor VIs, and could wire DVRs or values at will.  Then I hit the run button and complete crap.  I had to write a QD shortcut to replace all of the property nodes with their underlying VIs, and then the code ran just fine.  

0 Kudos
Message 12 of 15
(1,750 Views)

 

Paul, that VI would have to be part of the password protected vi, so its simply a programmer mistake. Personally I see  no problem there.

0 Kudos
Message 13 of 15
(1,719 Views)

@paul_cardinale wrote:

 

Inlining this would open the BD even if password protected.

BDO.png


If that were inlined as is you are correct that could cause problems. But the compiler is essentially looking at what that property is referencing and before inling would realize it needed to open and pass a reference to the original block diagram. At that point the compiler may decide not to inline at all, or it would generate code to open that reference from the diagram being inlined to and pass that reference to the node. 

 

Either way, the original semantics would be maintained.

0 Kudos
Message 14 of 15
(1,687 Views)

 

A password protected VI can open its own block diagram without the password.

 

"If you weren't supposed to push it, it wouldn't be a button."
0 Kudos
Message 15 of 15
(1,669 Views)