Standalone exe and properities

[urs boegli]

I've built up an application (about 200 VIs) where i want to have a
standalone exe version which will be used in the production floor.
This was no problem until I added some functions from the 'Application
Control' Sector. Also I load some vis dynamically. I cannot remember
where Iive seen the information about these problöems. Any hints?
Thanks
Urs

[Mads]

Can you specify which application control functions you have added?

There are e.g. some methods that are not supported in built applications. You can e.g. not set the value of dynamically called VIs using the "Set control value" method (invoke node). In built applications you have to do that using e.g. a functional global (I normally use a string array with the name of the VI in one column and the parameters flattened in another...Then the VIs search the list and find their parameters).

Mads

[Mads]

Actually the set control value method works fine...I just discovered - that is if the front panel of the called VI is included. The first time I encountered this problem using "set control value" I contacted NI but they never pointed out that, so I found a workaround and have not tried it since, however now I saw the following post and tested it. So that's probably not your problem, but anyway...:

http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=135&HOID=506500000008000000AB4F0000&UCATEGORY_0=_49_%24_6_&UCATEGORY_S=0&USEARCHCONTEXT_QUESTION_0=set+control+value+does+not+work&USEARCHCONTEXT_QUESTION_S=0

[urs boegli]

I use some 'frontpanel window.open' and set visibility to controls. I
read a list of the names of the controls, too.
These are spread over a few sub and sub-subVIs.

Thanks
Urs


Mads schrieb:

>Can you specify which application control functions you have added?
>
>There are e.g. some methods that are not supported in built
>applications. You can e.g. not set the value of dynamically called VIs
>using the "Set control value" method (invoke node). In built
>applications you have to do that using e.g. a functional global (I
>normally use a string array with the name of the VI in one column and
>the parameters flattened in another...Then the VIs search the list and
>find their parameters).
>
>Mads
>
>