OK. I will try to improve to find coercion dots in an entire project. In theory it should be possible to find all called subVI's, find the structures existing within them, and then flag for coercion within those structures. (Repeat the same for the top-level VI as well).
Buts it's a lot of work! Will try to use parts of "Find all used and unused VI's" that I modified for E Blasburg (and which are part of the OpenG tools). At least that should give me a reference to all the VI's in a project. Let me know if you need a copy of the "Find all used and unused VI's". It is a very useful utility to find junk VI's inside projects and open/delete them with a single click. I doubt NI will change the diagram/coercion? Properties in the next couple of revs, because I just saw a release from them about some sort of VI advisor product that does exactly this sort of thing: examine a project for style, efficiency, etc and recommend improvements. Neville. -----Original Message----- From: David Edwards [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 24, 2004 4:53 PM To: Neville Dholoo Subject: Coercion dots Neville: A follow up on the coercion dot problem. You may have noticed that the code I sent only finds dots on the open diagram, not inside structures. To find those requires the use of class constants for WhileLoop, Sequence etc. as well as Diagram. That way, one can spin down the list of diagram objects, opening the structures as needed. If you find out how to do that let me know. Regards, David
