X___

Attached are two VIs containing the two objects discussed above. Place them in your "Favorites" palette, choosing to "Place VI Content" for easy access. Types Must Match.vi Type Specialization Structure.vi

For those who have been playing with malleable VIs, the Type Specialization Structure has probably become a common sight and much abused tool. The basic use of it is that if the action it performs is meaningless given one of the inputs, the included code will break and the next case will be tried. This is great, but sometimes, it can be difficult to think of all possible variants of an action, and in particular, if the action needs to be different for two or more types, but two or more types are compatible with different codes, how to make sure which code will be executed with what type? Enters the Types Must Match function: I found this little gem in... Hidden Gems, within an odd-looking VI which I felt compelled to check out, Debug Write.vim Open its diagram and light will shine, opening grandiose vistas and parallel universes remaining to be explored. Of course, as the comment on the diagram says: "This structure and the type-testing primitive functions it contains are not public LabVIEW features. They are experimental and should not be edited, copied, or used in other VIs without conducting extensive testing. See Context Help for details." Here is the context help for Types Must Match: My apologies if this all well-known among expert users, but I couldn't find it mentioned otherwise on the site...

Including comments such as "/* Oh well this can get messy."? You've probably graduated from the Concise-Better-Yet-No-Comments School, like I did... I'll leave it to the experts as I haven't the slightest clue which API you are talking about.

I'll take that as a no...

That might qualify as thread-resurrection-and-hijack, but is there any chance to get a 64-bit compatible version of labpython? Currently, after correcting the erroneous path of lvpython.dll in the "PYTHON New Session" VI, loading fails with this pretty explicit message:

Somebody ought to fix that OpenG front page... Graphical!

It does indeed work. Nice workaround. Well that would require me to get into scripting first! But if I ever did and worked on it, I think there is one thing I'd tried to improve on this otherwise amazing toolbox: I'd make sure that wires don't originate necessarily from the "center" of the object, but rather from a natural starting point, such as one of the object's borders, for instance. Kudos anyway! PS: actually there is one more thing, which I think would be a nice addition: when modifying a "weirded" wire, it would be nice to reset the former "weirding" in order to avoid having crooked connections. "Cleaning up" the wire is not a very reliable solution, as NI's "cleaning" algorithm has some uncontrollable tendencies to whip wires around. PPS: and this: allow selecting multiple wires and apply the "weirdiness" to all selected branches.

I have installed the RCF plugin and it is quite amazing. However, I have discovered this little bug. In this situation: Choosing "Round Corners" will result in this: No other "Weird Wire" choice results in an error, so I suppose that there is some weird calculation somewhere, although I could not spot one after a cursory glance at the code.