04-29-2015 03:53 PM
Inlining this would open the BD even if password protected.
04-29-2015 05:53 PM
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.
04-29-2015 11:39 PM - edited 04-29-2015 11:39 PM
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.
04-30-2015 11:29 AM
@paul_cardinale wrote:
Inlining this would open the BD even if password protected.
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.
04-30-2015 12:26 PM
A password protected VI can open its own block diagram without the password.