strange paths when using Get VI Dependencies

[jessica_kh]

Hi,

This is more curiosity than a request for help.

I have implemented lists of user generated dependent Vi's and Ctl's as part of my system startup as a reference and I came up with a strange anomaly.

One Vi has two more instances in the dependency list

C:\Users\me\SYSTEM\Find_a_TP.vi

C:\Users\me\SYSTEM\Find_a_TP.vi\9eaf5943-a248-4e95-b650-d3c6088aceb2.vi

C:\Users\me\SYSTEM\Find_a_TP.vi\cac5c9ea-292d-43f3-909b-b2ec2b433a2c.vi

I removed the vi from the system and all 3 entries were removed, putting it back and all three were returned with the same extras.

It is not re-entrant and has a single call.

Does anyone know what these are please

Jessica

[rolfk]

The numbers at the end indicate cloned instances. Your VI is set to be reentrant (either using a clone pool or explicit clones)

[billko]

---

@rolfk wrote:

The numbers at the end indicate cloned instances. Your VI is set to be reentrant (either using a clone pool or explicit clones)

---

That's news to me.  Awesome.

[jessica_kh]

This is what I thought it was, but the vi is not set as re-entrant and I have never set it as a clone as I would not know how. 

As it is not set as re-entrant how else can it become a clone. 

[Kyle97330 · Accepted solution]

Those are likely calls to .VIM files in that VI.  If you look you will probably find 2 of them in use, which could be 2 of the same one or 1 each of two different ones.

VIMs look like that because each time you put it on a block diagram, it creates a tiny copy of itself that embeds itself onto the block diagram, which is why it looks like a VI has another VI it it.

If you set the "Keep express/malleable?" setting to False, it should go away and you will instead see the VIM in the list.

[jessica_kh]

I was not aware of VIM files and it seems that \i used one without knowing. That VI has a "Is Value Changed" function that now I  see is a VIM.

Thank you. It was annoying not knowing what was happening.

Jessica