Vladimir Drzik Posted July 21, 2009 Report Share Posted July 21, 2009 (edited) This is what LV help says: A reentrant VI can have dynamic dispatch terminals only if the VI shares clones between instances. This VI preallocates a clone for each instance. To fix this issue, you must either change the terminal in the connector pane to not be dynamic or change the reentrant execution in the VI Properties dialog box to Share clones between instances. Do you know why this is so? Edited July 21, 2009 by Vladimir Drzik Quote Link to comment
ned Posted July 21, 2009 Report Share Posted July 21, 2009 This is what LV help says: A reentrant VI can have dynamic dispatch terminals only if the VI shares clones between instances. This VI preallocates a clone for each instance. To fix this issue, you must either change the terminal in the connector pane to not be dynamic or change the reentrant execution in the VI Properties dialog box to Share clones between instances. Do you know why this is so? Dynamic dispatch means that you don't know at compile time which VI will execute, and it would be impossible to preallocate a clone of an unknown VI. 2 Quote Link to comment
Vladimir Drzik Posted July 21, 2009 Author Report Share Posted July 21, 2009 Dynamic dispatch means that you don't know at compile time which VI will execute, and it would be impossible to preallocate a clone of an unknown VI. Now I got it. Thanks Quote Link to comment
Aristos Queue Posted July 23, 2009 Report Share Posted July 23, 2009 Dynamic dispatch means that you don't know at compile time which VI will execute, and it would be impossible to preallocate a clone of an unknown VI. We talked about the possibility of cloning *all* of the possible subVIs that you might call -- after all, it is a finite set of VIs that might be invoked -- but ultimately we decided that was very rarely useful, to the point that it was better to just steer everyone into the share clones model. If you need some state for your function stored in an uninit shift register, the recommendation is to put that shift register on a static dispatch VI that calls the dynamic dispatch VI as a subVI. Quote Link to comment
Brandyn Posted October 11, 2012 Report Share Posted October 11, 2012 This post is still relevant...this really helped explain a problem I was seeing on some RT code Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.