Another use for the disable structure (Bug or Feature?)

[Wiebe@CARYA]

Hi,

I always use a lot of dynamic VI's in my projects, and sometimes I need to
pass parameters to them. I use Set Value methods.

One problem is that when you build an executable, the application builder
(AB) removes the panels by default, and the Set Value method will fail... I
know you can change the AB settings, but I was getting tired of that (and
had some free time). I also know you can change the VI properties so AB
won't remove the front panel...

But I started looking for things that tells the AB not to remove the front
panel.

I found out that the FP won't be removed when the VI has an event structure.
And it turns out that this works even if you put the event structure in a
disable case!

I'm pretty sure this isn't supposed to happen. I'm not so sure if it's
usefull since it might change over versions (I use 8.5.1), but I thought I'd
share it anyway...

Regards,

Wiebe.

[tst]

You can also just create a property node for one of the controls.

[TCPlomp]

Just today I had a problem with a VI with a diagram disable structure that would compile but the FP of the executable was mallformed and cause the whole app to crash.

So I stay away from diagram disable structures in execution code.

Ton

[Wiebe@CARYA]

"tst" <x@no.email> wrote in message
news:1216732207986-748619@exchange.ni.com...
> You can also just create a property node for one of the controls.

Sure. But that would actually do something ;)...

You can also add the VI to the list of dynamic VI's. That will also tell the
AB not to remove it's FP. Strange thing is that if you use a static VI
reference, the AB doesn't understand that you are going to use it
dynamically... Seems pretty obvious to me...

Regards,

Wiebe.

[TCPlomp]

Wiebe,
how do you load the dynamic VI into memory?


If I use the above method I have no issues with FP showing.

Ton (in 8.5.1)

[Wiebe@CARYA]

"TonP" <x@no.email> wrote in message
news:1216735809235-748676@exchange.ni.com...
> Wiebe, how do you load the dynamic VI into memory?<img
src="http://forums.lavag.org/uploads//monthly_07_2008/post-2399-1215532702.p
ng"> If I use the above method I have no issues with FP showing.Ton (in
8.5.1)

Almost the same... But I usually don't make my static VI references strictly
typed, because there is no need for that.

I've tested it, and making the static VI reference strictly typed doesn't
make a difference.

I suppose you've added the VI's to the project as dynamic VI's, which makes
it work just fine. But I usually forget that at least one for for a new exe
for each new dynamic vi...

Regards,

Wiebe.