MagicWand

I've tried to do some GOOP in LV 6.02 and I wanted to use Named objects/instances. It is fairly easy to set the name of an object, but then if I want to read the name of the object later on, how do I do that? The private functions "Get Data" and "Get Data to Modify" only return the Data from the Object repository, not the name. Of course I can in addition call the Object repository using the input method "Get Statistics", but is this the only way to get hold of the name? I don't want the statistics, I only want the Data and the name in one go. And I also don't want to store the name as part of the Data as what could be another solution.

Will I run into troubles if I try to convert the DQGOOP system from 7.0 to 6.1 to 6.02 ???

I couldn't edit my first post, so I add yet another question here: I looked at the diagram of <Class> Open Object Reference.vi. I'm no expert, so why is Flatten to String and then Flatten from String used in the diagram? Wouldn't a Type Cast do the same job ???????

I finally managed to install OpenGOOP, manually into LV 6... (Some VI was missing, which I found in the OGLIB_String package.) I know GOOP 1.0 only was a bunch of shift registers, build arrays and such, and was quite slow, but is OpenGOOP faster? And how is it compaired to GOOP 2.0? BTW, how is it with OpenGOOP and named objects. I have used that with GOOP, so how do I do that in OpenGOOP? Another thing I wonder about is: Why is the Default Data Cluster embedded in a VI? Wouldn't a Default Data Type Definition.ctl do the same job. The Default Data.vi seems quite obsolete. Why store almost nothing (as in this case) into a VI? Shouldn't <Class> Data Core Task Enum.ctl be on the front panel of both <Class> Data Core.vi and <Class> Object Data Core.vi? There was no connection to the type def. on FP of one of those VIs, I don't remember which.