I tried putting try-except blocks around calls to Skye4COM but it didn't help.
Is there a global exception handler that I can replace in order to catch the uncaught exceptions? Thanks, Jack Sunday, November 11, 2007, 1:18:18 PM, you wrote: > JLIST wrote: >> I'm using the Skyp4COM object in a delphi app. Sometimes the >> application (not the COM object itself) shows error message dialog >> boxes from the COM object. There is an error event from the COM >> object and I'm catching that, but this doesn't help. > Are you sure you're catching the right exception type? >> The app still >> shows these error messages. Skype4COM developers confirm that >> the COM object is not showing any error boxes. I checked all my code >> (only a few files) and there is no ShowMessage or MessageBox. The >> error message title is the file name of the application. I wonder >> if this is some default behavior of COM objects, and if there >> is a generic way to prevent Delphi apps to show COM errors? > While the message box is showing, press the "pause" button in the IDE. > Then bring up the call stack, and you'll see exactly who's displaying the > dialog box. > A likely candidate is Delphi's built-in exception handler. It gets invoked > whenever an exception goes unhandled while a control's event handler is > active. _______________________________________________ Delphi mailing list -> [email protected] http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
