That's pretty cool, David! The possibilities really makes the mind wander and wonder. I'd be interested in hearing about and seeing some examples of other neat utilities people have been able to put together using these "exposed privates". Perhaps a LAVA discussion forum could be created for the purpose of investigating these newly discovered Scripting toys. That way the Advanced LabVIEW user-community could help provide basic tech-support and documentation.
Regards, -Jim Kring > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Edwards > Sent: Monday, March 22, 2004 6:16 PM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED] > Subject: Warnings & coercion dots (Was - All those things) > > > Stephen: > > LabVIEW now has the very nice warnings feature that is very good for > improving code reliability. Unfortunately, coercion dots do not show > up as warnings. > > Finding the "diagram" property in the code Norman pointed to, allowed > us to write a nice utility to scan a complete project for coercion > dots. > > David Edwards > FemtoTek, Inc. > > > Standard warning that anything "that we try to hide" > > a) may or may not be supported in the next version of LV > > b) probably has never been introduced to tech support so > they won't be > > able to help you c) may break (read: crash) if used outside of very > > specific context. > > > > Proceed on the theory that if you're using it, you're on > your own. We > > don't typically hide things that we think customers can actually > > safely use. > > > > Pojundery, > > Stephen R. Mercer > > -= LabVIEW R&D =- >
