Conditional Disable for Build Specifications

[jmorris]

The new Conditional Disable structure seems like a really neat idea that was almost implemented perfectly.  😉

My application has a regular and a "Lite" version that both use the same VIs, but in a couple places it checks a global variable to see whether the regular or Lite code should be run.  I would like to implement this with Conditional Disable structures.  However, since apparently you can only set Conditional Disable Symbols on the project and target level, not on individual build specifications, I don't see a way to do this within the same project.

Creating a second project seems like a decent workaround, but it seems wasteful/redundant to have all of the same VIs and settings, with only the C.D. Symbol different.  Not to mention having to keep both updated as I add or remove VIs to the project.  Does anyone know of a better way to accomplish this?

Thanks!

-Joe

[Chris_Cilino]

Joe,

I can see why you'd want to use the Conditional disable for you application. However, from the help I get the impression that this structure was intended to provide information about the system and have your application change its behavior based on some value of the system (like os). Outside of that, the user has to change the value of the symbol manually. I think a better approach would be for you to include an encrypted file with your program that determines it's behavior. On load, it would read and decode this file, then propagate the value to case structures throughout your program. I think using the case structure with some file or global variable might be a better\easier way to go.

Chris C

[jmorris]

Ah well, I figured it couldn't hurt to ask in case I had missed something.  😉  Thanks for your reply.