This is from the 1/14/03
info-labview digest:
"
Hi, Tim
As you know, to distinguish between public and private methods, GOOP uses the LLB-top-level flag. Public methods are top-level and private method are non-top level.
But GOOP does one more thing with private method VIs. They are checked as "System VI", a property which make them invisible in the VI hierarchy and in the "VIs in Memory" application property, unless their panels are open. You can upgrade to the new GOOP wizard, downloadable from http://www.endevo.com/default.asp?lang=eng. It doesn't check VIs as system VIs. It is compatible backwards, so perhaps you can "repair" your existing GOOP objects if you use the new wizard, but I'm not sure. S
ince you can store objects in both directories and in LLBs with the new wizard, perhaps it helps to convert from LLB to directory and back to LLB again.
If the above doesn't work, you can use these two VIs to uncheck the "System VI" property:
1) C:\PROGRAM\National Instruments\LabVIEW 6\project\goopwiz.llb\Hide System VIs.vi
2) C:\PROGRAM\National Instruments\LabVIEW 6\vi.lib\utility\libraryn.llb\Librarian List.vi
Use (2) to create a list of VIs in your GOOP object LLB. Then loop through all the VIs and use (1) to uncheck the property.
If you want to read more about this, you can search for the string "Invisible VI ?!?" in http://www.searchview.net/, during 2001, in the info-labview archives. Then read the postings with the subject "Invisible VI ?!?".
Hope this was helpful!
Andreas
"
