From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-11-2010 04:18 PM
05-11-2010 04:20 PM
Why would you think a typedef needs to be re-entrant? It's just a definition of a type - it holds no data. Therefore, it cannot be made re-entrant.
Exactly what kind of "strange behavior" are you seeing? Care to post some code so others can diagnose it?
05-11-2010 04:35 PM
05-11-2010 04:42 PM
Whether it is a type def or not, a control is simply a variable. It does not have re-entrant properties. It can be written to from any subvi that has access to its memory space (control reference). It can be the subject of race conditions also (writng to its memory space from several subvi's at one time).
05-11-2010 04:48 PM
OK. Here's a related question.
In the Execution drop down of the VI Properties, the Help says "Note The Reentrant execution option must be the same in a parent dynamic dispatch member VI and a child dynamic dispatch member VI" I'm trying to understand who they are referring to as the 'Parent'. I have an upper level VI that only gets called once, but the subVIs it calls may have upto 16 instances. That note, however, makes it sound like the Parent (in my case, the top-level VI) also needs to have that 'Reentrant' checkbox checked. Is this true?
05-11-2010 04:56 PM
If you are using Dynamic Dispatch VIs, yes the parent vi must match the children. If one child is re-entrant, all the children and the parent must also be re-entrant.
The parent is the main instance that was originally created. That does not necesarily mean your top level vi. The parent is the main instance of a class and the children are created from this main instance. Not sure about my terminology, I hope its right. I understand the concept, just hard to explain. There are some good examples on Dynamic Dispatch VIs. Use "Find Examples" and search for Dynamic Dispatch.
05-11-2010 05:08 PM
05-11-2010 05:11 PM
05-12-2010 01:42 AM
05-12-2010 05:18 PM
As a recap, I have 16 instances of my app (but in VIT form) running. I can tab around and they're all there. However, two things I've identified (thus far) are the (1) my ActiveX Browser won't communicate when I type in the IP address of the Radio in question. If I bring up the app VI by itself (outside of the factory), I can login to and communicate. Also, there is a UserInfo area where I keep the user upto date on what's happening. Normally, I can click the "Clear User Info" button, and it does. While in the Factory, unless I'm seeing things, not only did it not clear the UserInfo assigned to Radio1 (the one where I clicked), but instead it cleared the userInfo for Radio12. Not even sure where to begin.