Darren: That works as long as your Move doesn't create a copy. It doesn't work if you
a) wire True to the Duplicate? terminal or
b) wire in an owner that is on a different VI.
If you do either of those two operations, I am not sure how you're supposed to get the duplicated object. I'm surprised there isn't an output parameter that is the duplicated refnum.
Ok, I understand now...I've only ever used the Move method to move (not copy) an object within the same VI. For your case, I see how adding that output would be useful, and I've kudoed your idea. For now, here's the best workaround I can think of. Assuming you've given your source object a unique label, and after you've done the move/copy, call this VI:
vi.lib\Utility\traverseref.llb\TRef Find Object By Label.vi
You already have a reference to the owner of the newly moved/copied object, and assuming it has a unique label, your code would look something like this:
Another developer offered another workaround that works on the block diagram. This helps if you don't have a unique label (i.e., if you're making multiple copies of the same object within the same owner):
Use the Create New Object to create a sequence structure in the owner
Move your object into the sequence structure
Use the sequence structure's properties to get the only object inside the structure
Use the Remove Structure method to remove the sequence while leaving the contained object behind.
Obviously would be better to not have to use these workarounds. I'll add my kudos.
Yet another workaround... After you do the move, get the selection list from the target BD or FP. This will contain references to all the moved code. You will need to show scripting functions to see the selection list property, but you have probably already done this.
