Updating strict typedef input to recursively called VI

[MartyS]

I have a VI I call recursively with VI server. One input to the VI is a enum defined as a strict typedef. When I change the typedef and select Apply Changes, the change propagates everywhere but the recursively called VI. In fact, the change introduces an enumeration conflict (input to Call By Reference Node used in the recursion). The conflict goes away after I manually rebuild the Open VI Reference, its strictly-typed-VI constant input, and the Call By Reference Node.

The recursively called VI was open when I changed the typedef, so it was in memory. In fact the change did propagate to the typedef input on the front panel, it just didn't make it to the Open VI Reference, its strictly-typed-VI constant input, and the Call By Reference Node.

Same behavior observed if the recursively called VI is made non-reentrant.

Is that expected or desirable behavior? If so, why? It's a pain to have to change the recursion setup manually; indeed it's counter to the main benefit of typedefs.

Thanks,

::Marty

[Ben]

If I read you correctly, you are looking for the same thing I am!

See Daren reply to my query in this thread.

http://forums.ni.com/ni/board/message?board.id=170&message.id=191138#M191138

Were he says that automatic updates are not possible and NI has it on their wish-list.

If that is not what you want, please some demo code along with instructions so we can be of more help.

Ben

Message Edited by Ben on 06-22-2006 02:30 PM

[MartyS]

Ben: Thanks, that's helpful. That's basically what I was looking for. Luckily, there's only one recursive call in my whole application--so far--so I only have to do the manual update in one place.

::Marty