"Jamie Dale" <j.dale@turboz.net> wrote in message
news:4484d979@newsgroups.borland.com...
> Admitted lol. Still, it stops that blinkin popup message
> though doesn't it!!!!!!!!!!!!!
That doesn't make it right, though.
> please try to understand how annoying that popup message
> is to those of us that are less experienced than yourself.
Then you need to learn the proper way to use things so the exceptions don't
occur in the first place.
> To us, it means nothing other than 'graceful' and it just becomes
annoying!
It is annoying because you let it continue to annoy you instead of fixing
what causes it.
> I don't mean to slate Indy but the point is, when your not very
> experienced and don't know what it means, the message is just a nuisance.
Then you should read Indy's documentation and articles, because the meaning
of that message is explained.
> >You should trap this error using a try..except.
>
> Erm, isn't that what I've been saying?
That depends on WHERE the exception is thrown from to begin with. On the
client side, it is almost always an error condition that needs to be handled
in your own code. Like I said, the exception only occurs when
reading/writing to the socket, so if it is closed unexpected then your code
needs to be able to recognize and handle it.
> I try to fix and in this case the fix was the Indy recommended Bandage
> which you yourself posted!
That is not what I was referring to.
Gambit
