🚀 go-pugleaf

"JD" <nospam@nospam.com> wrote:

> Why can't I catch ESocketError?

Are you using the socket in non-blocking mode?  If so, then
the actual work of Open() is being executed long after your
code flow has already flowed past your error handling code
altogether, thus it is no longer available to catch errors.
In which case, you should be using the socket's OnError event
instead to handle the error.  You can set the ErrorCode
parameter to 0 to prevent the eception from being thrown in
the first place after you handle the error.  For example:

    void __fastcall TForm1::Button1Click(TObject *Sender)
    {
        ClientSocket1->Open();
    }

    void __fastcall TForm1::ClientSocket1Error(TObject *Sender, TCustomWinSocket *Socket, TErrorEvent ErrorEvent, int &ErrorCode)
    {
        MessageDlg("Socket Error: " + AnsiString(ErrorCode), mtError, TMsgDlgButtons() << mbOK, 0 );
        ErrorCode = 0;
    }


Gambit