It would be nice if I could set the conditional disable settings in the build settings.

This would allow for multiple build settings that could incorporate into a single project file.
I have the feeling this can be done with separate lvproj files but that feels like a workaround.

Any thoughts on this?

Ton

I think it would be cool if the disable structure had an input like the Case structure i.e. boolean, enum, string, etc

Dan

What kind of usage does this have over the current disable structure?

Ton

The advantage would be I could understand how it works. I haven't been able to understand the conditional disable strucure.

Granted it doesn't take much to confuse me.

Dan

I also have wanted this, and made a feature request for it a while ago. Seems like a pretty reasonable request. Conditional disable flags affect the entire project, and the build settings build the project into an executable.

You set symbols for the entire project (by right clicking on the project in the project tree, if memory serves) and then you choose one of the symbols to switch all the structures throughout the project. I assume the help for the structure covers this in more detail.

Wow I never realized it was tied to the project. No wonder I missed that. Thanks!

Learn something new every day

Conditional Disable are project and target based. So you could have symbols just for specific targets or global symbols that effect all targets.

I agree

So far I've just been having to remember to set the right conditional variables before I build (and make sure everyone els knows about them...)

Setting this up as two builds inside the project would be cool...

Ditto,

One case in point, I have two target test stands for automated testing as part of product delivery. One has additional functionality (mine) and the other has non-disimilar equipment performing the same task (theirs). In the mid-level equipment code, I have added Conditional Disables to handle the differences between the two test stands.
Countless times, I went to deliver new code, only to realize that I forgot to change the Conditional Symbol.

Having the Build Spec's handle this would certainly make multi-targetting much more streamlined.

Unfortunately, I still follow the practice of Remove Symbol, Add Symbol.

I totally agree. We are actually reading the lvproj file (it's XML) and modifying the Conditional Disable symbols programmatically and then reloading the project so that we can build multiple flavors of our product. It's not terribly hard, but there should most certainly be VI server access to the symbols.

You can just use a Symbol Setup with a string mine and theirs. In your code you use the same symbols with these values.
Or just use mine and default.

Well I don't think that's necessary, changing the Conditional Disable Symbol forces a recompile of the code. That means all of the code inside the project shouldn't be running, which can be a challenging task.
The possibility to select another lvproj for a build is probably intended to cover this gap. But an additional page in the build settings is preferable.

This item shows a problem in my developing workflow. I considered the lvrproj file as code independent. But now it seems like it is tied to the code as well, and should be checked in and out.

Ton

Maybe I'm doing this wrong, but when I switch between conditionals, I right-click the project in the "Project Explorer" window and select "Properties..."
In the "Conditional Disable Symbols" section, the only options I see are "Add" and "Remove Selected Items". So far, my only solution is to first remove my symbol, then re-Add it with a new value.

Is there a cleaner way to change Symbols in a project? That would surely make my day.

Cheers,
-H

I seem to remember this with LV8.0. Starting with LV8.2 (I think) you can double-click on the value you want to change in the list and edit it straight away.

Even More reason for me to push (read: beg) for an upgrade. Thanks.