Malleable VI broken wires... NOT!

[1984]

What version of LabVIEW are you using?  I know this was a major issue in the compiler that many were up in arms over.  I'm mostly certain it has been fixed.  I don't remember exactly what versions were involved and too lazy to go digging.

---

Its LV2022Q3

[Darren]

---

@crossrulz wrote:
Granted, he goes full-bore "avoid VIMs like the plague".

---

My specific guidance is that really simple VIMs like Remove Duplicates from 1D Array, Enum to Array of Enums, or Synchronize Data Flow are probably ok. But other than the really simple ones? Yes, I avoid VIMs like the plague. Nested VIMs, VIMs with LV Classes on their connector panes, VIMs that try to get really fancy with Type Specialization Structures... no thanks!

[paul_a_cardinale]

---

@crossrulz wrote:

---

@BertMcMahan wrote:

That's interesting- I recently had an issue where a VIM inside a TSS inside a VIM was corrupting things, and getting rid of the VIM inside the TSS actually fixed my "This VI will not compile" error. I'd fix it, save everything, close, and reopen it and bam it was corrupted again.

---

A VIM inside of another VIM is a known issue.  It is not 100% going to break things, but, anecdotally, seems to be very commonly causing issues.  I'm pretty sure Darren N talked about this in his Ludicrous Ways to Fix Broken LabVIEW Code presentation.  Granted, he goes full-bore "avoid VIMs like the plague".

---

For an extra-hair-pulling experience, try putting a malleable inside an XNode.

[IlluminatedG]

---

@paul_a_cardinale wrote:

---

---

For an extra-hair-pulling experience, try putting a malleable inside an XNode.

---

*shudder*

[1984]

I had no real prior experience with malleable VIs, so it interesting to hear that besides the basic ones people should rather avoid using them. Too bad that I've just finished converting fair amount of VIs to vims.

For now my project works and compiles to an exe, so I leave it like this but I keep it in mind that if later on the malleables start giving me a headache I might need to convert them back to normal VIs.

thanks everyone.

[wiebe@CARYA]

---

@1984 wrote:

I had no real prior experience with malleable VIs, so it interesting to hear that besides the basic ones people should rather avoid using them. Too bad that I've just finished converting fair amount of VIs to vims.

---

If we don't try, and report the problems, it won't get better 😋.

It does seem to get better, but when the steps to reproduce are hard to define, finding a solution can be very hard. It might also be a niche, so there might be more pressing matters.

I don't hesitate to use them for the 'trivial' stuff. Typically, making string conversion (e.g. replace  ' with ") work with scalars, 1D arrays and 2D arrays, simply works great.

There places where I had problems (multi level recursion, long lists of specializations, CLFN calls, mixed with dynamic dispatching...) I didn't really expect it to be care free.