Leaderboard

Wow, guys, make drjdpowell feel bad, why don't you?

This is one of the first default settings I change. I think icons on the block diagram are unnecessarily large and provide no additional value over the terminals. You're actually the first I've (knowingly) come across which actively prefers the icons... you're like a LabVIEW unicorn

Yes, I can help, I have a lot of experience with yak shaving. This video should give you all the information you need. Please follow its instructions carefully, as an unshaven yak is something to be taken very seriously.

An experiment. My previous subVI redone to be more like ShaunR's style:

I greatly prefer the icons (as James knows) because: 1) They are easy to see. I am very focused on the interface and I want the terminals to stand out. 2) They sometimes contain additional information, and I consider them more aesthetically pleasing. 3) Saving space is not a concern because of the way I design my applications. A class method (and very nearly all my VIs are methods in classes) usually has the terminals for the owning class, error terminals, and maybe an additional input or output (occasionally a couple of each). I have plenty of room for these on the block diagram, and I want them to be highly visible.

For some reason, I seem to recall that the large terminals were introduced at the same time as NI's Lego MindStorms software. Aristos Queue is the 1%! Occupy the NI Forums! Don't buy into queues and LVOOP! Down with him and his ways! (Only kidding )

I hate large icons. Aristos Queue loves them. If I had my way, they would have been gone long ago. Unfortunately, AQ always argues to keep them around. But since he's so badass in just about everything else he does around here, I'll pick my battles elsewhere.

This is the kind of code someone using icons ended up with... IUsually when someone uses icons they don't really know LabVIEW

As requested, here is this simple tool intended for providing an easy way of calling properties and methods. I thinks it's pretty intuitive and works as other similar applications. Select the LV version, the class and the desired properties or method. Press "copy" to have the function in the clipboard and paste it in a block diagram. Known issues: The description box doesn't show anything, because I haven't found a way of programmatically retrieving it. Any idea will be welcome. Some properties can't be created this way. For example, try Generic -> Owner and you'll see the deprecated property is created instead. Maybe not all properties and methods are included and can be some repeated. You can play with the txt files to add and try ned props/meths. The search capability was added as an afterthought and I would prefer to have it better integrated. But still useful. Please tell me any improvement or idea you get. Saludos, Aitor