I thought about trying an iteration on "callees" so that the scheme would work even if more functionality (and thus more subVIs) were added. (I got caught first by Simple Error Handler calling General Error Handler.) Originally, I had hoped to avoid subVIs entirely, but I managed to trigger errors myself and figured they better give some feedback to the user.
The "Caller in memory" sounds like it might be a practical solution. Iteration on "Callees" looks messy. Maybe a simpler response than the Simple Error Handler is best. I'll look at it tomorrow.
...I just tested it but in LabVIEW 6.1 and higher the General Error Handler.vi has some more subVIs for it's internal user error code database and therefore your
VI will always pop-up.
Not sure how to fix that LabVIEW version dependant. Maybe try to avoid any VI in the list which has any Caller in memory?
Rolf Kalbermatter CIT Engineering Nederland BV tel: +31 (070) 415 9190 Treubstraat 7H fax: +31 (070) 415 9191 2288 EG Rijswijk http://www.citengineering.com Netherlands mailto:[EMAIL PROTECTED]
...> GhostBuster.vi, now > available on http://www.SULLutions.com/LabVIEW.html, flashes a large,> screen, or have their front panels closed...red warning on your screen when the only VIs, Globals, and Type Defs in memory are invisible because they are on the clipboard, off
--
EnWirementally,
Paul F. Sullivan----------------------------------------------------
SULLutions (781)769-6869
"when a single discipline is not enough"visit http://www.SULLutions.com
----------------------------------------------------
