build application with conditional disabled VI's still tries to load them ...

[Peter_Prinzen]

Hi,

we have a big LV-project with some "conditional disabled" or with a "switch" unused VI's. But LabVIEW still tries to load them when building an application (even when they are not used). Is there a setting to prevent this behavior? Something like "ignore unused/missing VI's during built"?

Thanks

Peter

[MoviJOHN]

When you say "Conditional Disable", do you mean you are putting the VI in a case structure, with a "F" boolean constant wired to the empty case?

If this is so, you should use the Disable structure instead.

[aputman]

You can define custom symbols in your project properties to use in the Conditional Disable structure.  I don't know if that helps you any.

[JÞB]

conditionally disabled structures conditions are evaluated at runtime.  Therefore, the "Disabled" code case cannot be removed during compile and must be loaded unbroken for the callers to compile correctly.

[Peter_Prinzen]

Ok, I understand;

So there is no way to prevent LabVIEW to load really not used (conditional disabled...) VI's during a build?

Maybe for future version?

Peter

[mikeporter]

Hey Jeff!
If the conditional disables are evaluated at runtime, that implies that there is a way to set the conditional symbol values -- or at least the user defined ones -- at runtime. Yes?
Mike...

[dan_u]

---

@JÞB wrote:

conditionally disabled structures conditions are evaluated at runtime.  Therefore, the "Disabled" code case cannot be removed during compile and must be loaded unbroken for the callers to compile correctly.

---

I don't think that's true. If it is evaluated at runtime that would mean the compiled code must contain the code from all conditions. This can't be true since the code for some (unused) conditions can be broken and it will still work.

The condition is evaluated at design time. When changing a disable symbol it will recompile the code.

[JÞB]

The difference is disable structure and Conditional disable structure.  unconditionally disabled code can be broken as it cannot run.  Compare that to a case driven by a constant- the unreachable code is removed by the optomizer in certain conditions (We won't guess what conditions prohibit this optomization and it has been changeing a lot since 8.6 to 2013 I imagine it will continue to evolve) however, Because the optomization is not garanteed to occurr the unreachable code cannot be broken.  This is simillar to the conditional disable symbols- they are not evaluated untill runtime and the condition may depend on variables external to LabVIEW.  So, all cases must be compilable.

@ Mike- Yup, I believe those symbols values CAN be manipulated external to the app instance (Certainly App.Kind comes to mind).  I don't have any experience doing that. 

[dan_u]

OK, let me rephrase my earlier post:

Unused cases in a conditional disable structure can contain broken code and the VI is still executable. I have that all the time, e.g. for VIs that can run both on RT and Host and use target specific functionality. So NOT all cases must be executable. The disable symbols thus CAN'T change during runtime.

App.Kind has nothing to do with disable structures. How would you link the two?

[MIG]

I think some of the pre-defined symbols are evaluated at runtime. For example "RUN_TIME_ENGINE".
But cases for custom symbols that you define yourself can contain broken code and still compile OK. I do this all the time as well.