LabVIEW Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 
0 Kudos
Manu56

"CloneName" and/or "Clonereference" property of a subVI reference

Status: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined. 

In the properties of a subVI reference, you can get the name and reference of the VI.


When The VI is re-entrant, with this property then you get the name and reference to the "Model" VI but NOT to the Clone associated to the subVI.

In scripting activities, it would be usefull to be able to get the name and/or reference of the Clone VI of an instance subVI...

 

For example, in development mode, I have a instance subVI of a re-entrant on which I need to put a breakpoint by scripting at runtime for debug purposes. This is something I actually can't do.

 

I think that's this is something easy and that might already exist (in private properties of subVIs ???) because when you double click on a subVI instance of a re-entrant VI, then the front panel of the clone (i.e. copy) of the original VI is opened. So there's somewhere a link between the subVI (reference) and the Clone VI.


(it's already possible in VI property to get the Clone name when this VI is re-entrant).

(Hope I'm clear...)

 

 

16 Comments
Manu56
Member

Thank you very much AristosQueue. Your help and involve is greatly appreciated.

Manu56
Member

Hi AristosQueue,
Back again... 🙂
Since VI express solution is not completely satisfying solution... my express VI should not be re-entrant and then making a copy paste of my Express VI will make fail my strategy...
So I'm looking to you express VI. Actually it works with VI reference, but I think I can make it works with subVIs reference...
Please correct me if I'm wrong... to achieve this I have to assume that the last subvi ref of the [subVI ref] array obtain through the property of a diagram is the last that has been put on this diagram... Can I be confident with this ?


thanks for your help...

 

PS : 

- Humm, it's also seem that there might be problems with this solution when making copy/paste action on the re-entrant VI (taht contains the X control) of your example... I Follow investigations...

- it could be very interesting to have the possibility to achieve actions (laucnh code through an event structure) when a VI is dropped as SubVI... just like the way you can do with a X control when you drop it on a front panel... I tried to manage this with your X control and making a VI opening its front panl when loaded but this is not possible for re-entrant VIs... how ever it won't be very clean...

AristosQueue (NI)
NI Employee (retired)

> Can I be confident with this ?

 

Oh... probably.  That isn't the defined behavior, insofar as that isn't a documented promise that we make. But it is the de facto behavior and I don't see any reason for it to change in the next few years.

 

> how ever it won't be very clean...

 

None of the solutions are clean. I've been complaining about this for years and trying to find a better solution. I continue to work to find a better answer for these scenarios. I wish I had a better answer for you.

Manu56
Member

Well, after many experiments, it's not solved... if at least the naming of the clones could have been consistent with the order of the subvis... but no...

Manu56
Member

Finally, this can be done quite easily with Express VI... I was searching tricky things but since each Express VI is an instance, so with a different name, it's very easy to find the corresponding suVI ref !

Can you tell me a litlle bit more about the drawbacks you know of VI express ?

- Overhead execution time ?
- Application Builder compatible ?
- Real time targets compatible ?
- Code size ? memory use ?

 

More over... if I could make directly a VI as an instance VI when dropped (and not a clone for re-entrant)... this would be even easier...

It seems that writing to the property "is an instance" in VI properties generate error 1043... not supported in this LabVIEW version. !!!???
I understand that an instance VI is not more than a simple copy of a VI, but VI express can make it transparently... can't we ?

Darren
Proven Zealot
Status changed to: Declined

Any idea that has not received any kudos within a year after posting will be automatically declined.