No custom runtime menu in compiled application for dynamically loaded top level VI

[alkazaa]

Problem occurs in LabVIEW 2011, SP1:

I have a main VI ("launcher VI") which spawns other top-level VIs by cloning them at runtime from a template VI (*.vit). The spawned clone VIs have a custom runtime menu. All works fine, in the development environment as well as in a compiled application.

Also a debuggable compiled application runs nicely, either running standalone or under control of a debug server, when I really do the debugging.

However, when controlling with thr debug server, the runtime menu is only visible (but not usable) in the controlled VI, while in the (remote) controlling VI the standard menu appears.

What do I have to do to make the custom menu appear  in the remote controller VI ?

-Franz

[mikeporter · Accepted solution]

I believe that this is a known bug.

I seem to remember a recurring issue with run time menus getting lost in compiled applications. However it only effects menus that you create using the runtime menu editor. If you build the menu programatically, which IMHO is better anyway, you don't have the problem.

Mike...

[alkazaa]

Thanks Mike!

I did indeed create the menu with the editor.

Guess I have to recode it now (my application is complicated enough to require debugging of the code in its compiled form).

BTW (and if you have time to answer 'bonus' questions):

I used the method of spawning VIs from a .vit template to control several functionally identical instruments with identical Labview GUIs from one PC.

Is there a more elegant way which you would recommend?

Regards

Franz

[mikeporter]

The currently-accepted "best practice" is to make the code that is now a VIT into a reentrant VI and use the asynchronus call node to launch them using "call and forget".

I believe that there are examples showing the basic technique.

Mike...