More XControl questions / issues

Question

XControl 1, X1, has two other XControls, X2 and X3, on its
block diagram
When I open a VI with X1 on it, the Init ability is called
for X2 and X3 three times each.  X1’s
Init ability is called one time.  (The
other VIs you see pop up are called from X2 and X3 as a result of Init
executing, so they illustrate the Init calls. 
They close when Uninit is called, and you can see as much when you close
the VI and project)
When I close said VI, the Uninit ability is called for X1
and called twice for X2 and X3.  This, of
course, leaves one instance of X2 and X3 left open.  Consequently, references and VI’s I opened as
a result of the Init call are left open (you notice the two subvi's still open). 
Once I close the project, the Uninit abilities are called
for X2 and X3, closing the remaining resources.
There is a file in the folder called log.txt I write to in
the init and Uninit abilities for each XControl.  If you open it after each step you can see
what I’m talking about.
Additional things: 
After I close the VI, but not the project, X2 and X3 are of course
locked.  When I right click “Unlock this
library for Editing”, LabVIEW crashes with a .cpp error.  http://forums.ni.com/t5/LabVIEW/Error-when-I-Unlock-Library-for-Editing-with-XControl/m-p/1009044#M4...
My real project loads the XControls (and executes the Init ability) as soon as it opens for
some reason, and makes it nearly impossible to edit them unless I close and open the
XControls individually, due to the .cpp error above.
Questions
Is it expected that an XControl an another XControl should be called more than once?
Why don't they get unloaded when the main XControl is closed and unloaded?
Why the .cpp error?
Tim Elsey
LabVIEW 2010, 2012
Certified LabVIEW Architect
Attachments:
XControl Forum Test source.zip ‏165 KB
XControl demo video.zip ‏3598 KB

Answer 1

Hello elset191
Here is the Corrective Action Request that references your issue.  I have included you as a customer whom this problem is affecting.
Request #: 302463
Description: XControls remain open after corresponding VI is closed and crash occurs, XControl cpp error in LabVIEW 8.6.1f1 (Fatal Internal Error: "ThEvent.cpp", line 184) 
I'm sorry that this has been a frustration to you.  The fastest way to resolve this issue appears to upgrade.  Have you attempted to reproduce this error in LabVIEW 2010 SP1?  I was unable to reproduce this situation in LabVIEW 2010 SP1.
The CPP error is due to some issue with how this has been internally developed.  It appears to have been resolved in LabVIEW 2010 SP1 as do the other issues you have been dealing with.  Can you please confirm this for me?  I am happy to further address this issue to ensure your success.  All the best!
P.S.  I have provided a link to the LabVIEW 8.6 Help simply for competeness.
Editing XControls that are in Use
http://zone.ni.com/reference/en-XX/help/371361E-01/lvhowto/editing_xcontrols_in_use/
Sincerely,
Greg S.