Paul,

One solution, that works very well in this sort of situation, is to invoke
the General (or Simple) Error Handler by reference.  But, make sure not to
open the reference (and thus load the VI into memory) until an error has
actually occurred.

Regards,

-Jim

> -----Original Message-----
> From: Paul F. Sullivan [mailto:[EMAIL PROTECTED] 
> Sent: Wednesday, March 03, 2004 5:19 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]; George Gatling (Contractor); 
> Hooper, David S OGUK-OGES; Howard, John; Jason Dunham; Smith, 
> Blair; PJ M; Rolf Kalbermatter; Greg McKaskle; Jim Kring
> Subject: RE: Detecting Lurking VIs (was Confounded and Ranting)
> 
> 
> Thanks, Rolf.
> 
> 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,
> >>  red warning on your screen when the only VIs, Globals, 
> and Type Defs  
> >> in memory are invisible because they are on the clipboard, off
> >  > screen, or have their front panels closed...
> 
> 
> -- 
>       EnWirementally,
>       Paul F. Sullivan
> 
> ----------------------------------------------------
> 
>       SULLutions              (781)769-6869
>       "when a single discipline is not enough"
> 
>       visit http://www.SULLutions.com
> 
> ----------------------------------------------------
> 


Reply via email to