[docs]
Finally, you should note that events are really evaluated (as if they were
called with eval()), so that errors are trapped, and a message box is shown.
This box reports the offending event name on the title bar, the error
message in its body and has OK and Cancel buttons. If you press OK,
Win32::GUI will ignore the error and go on with the dialog (the event, of
course, doesn't take place); if you press Cancel instead the dialog will end
(with return code -1). This means that for example if you define an event
like:
sub Button1_Click {
die();
}
your script will not die immediately at the click of a button, but the
message box will appear, reporting for example ``Died at script.pl line
73''.
[/docs]
I'm using XMLRPC::Lite with Win32::GUI and if the person's offline, they'll
of course get an error which (in X::L) results in a call to die(). which
brings up the "OK/Cancel" box. which kills the app on cancel. Not what I'd
like to happen. Anyone know a way _around_ this?
--
Robinson
[EMAIL PROTECTED]
