Leaderboard

How about this? It may require more testing to eliminate things like String controls that contain the search text, but that's easy enough (depending on the application).

The typecast node will never use the input buffer for the output. In fact not only will it copy the entire buffer, on Intel processors it will visit each element to put it into big endian format then visit each element to put it back to little endian. If an API requires users to typecast significant amounts of data, I would consider that a deficiency in the API that should be redesigned. For cases where the array elements are the same size, it would be possible to write a DLL that took both types and swapped the array handles. Be sure to configure both parameters as pointer to array handle then swap the handles.

Well what can I say. I am posting this from my new ..... Wait for it Ipad2 Yes, at the weekend I went into a shop and help both a Zoom and an IPad in my hands at the same time and played with them and the IPad won for me. Mind you all Sunday, I wanted to throw it in the bin. I was updating to IOS5 and it failed so went into recovery, then nothing I could be would get it working again. I uninstalled iTunes and reinstalled it, tried a laptop and a PC. On Monday morning somebody at work had a go and it worked first time. I did not know if I was really please or really pissed off. Anyway, I have had working a couple of days now and really like it, Lava looks great on the IPBoard app Cheers all Danny

Very nice...I always use the VariantDataType VIs, and have never thought about using Flatten to XML to get more info out of a refnum than what those VIs provide. Your approach looks solid...find the <Name> tag under the <ActiveXType> tag and you should be good: <LvVariant> <Name>Variant</Name> <Refnum> <Name>ActiveX Container</Name> <RefKind>ActiveX</RefKind> <ActiveXType> <GUID>{9B4CD3E6-4981-101B-9CA8-9240CE2738AE}</GUID> <Name>Acrobat.CAcroApp</Name> </ActiveXType> <Val>0x00000000</Val> </Refnum> </LvVariant>[/CODE] It's not often these days that I get to add something new to my LabVIEW bag of tricks...

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 )

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