Markus Mueller wrote:
> This also don't work. I never see my (extended) destructor beeing called,
> if it is called "Free" nor "Destroy". Also my memory usage is increasing
> if I just do "release". If I do Free I get memory errors but the memory
> usage is not increasing.
>
>
I suppose you hav
ier framework, freeware)
http://www.overbyte.be
- Original Message -
From: "Markus Mueller"
To: "ICS support mailing"
Sent: Wednesday, February 18, 2009 9:47 AM
Subject: Re: [twsocket] Freeing of sockets
This also don't work. I never see my (extended) destructor beeing called
Hello Markus,
Release post a message to a hidden window. when the message is received
Destroy is called. You can check that with the debugger.
Destroy call the destructor direct. Free checks for null value and then
calls Destroy.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/t
This also don't work. I never see my (extended) destructor beeing called,
if it is called "Free" nor "Destroy". Also my memory usage is increasing
if I just do "release". If I do Free I get memory errors but the memory
usage is not increasing.
Please, how is the realy right way to free the TWSocke
Destructor must be called "Destroy", not "Free"
Markus Mueller wrote:
> Hi Wilfried,
>
> I have created an destructor Free, which inherited runs Free of
> TWSocket. This
> Free is never called; can anybody tell me why?
>
> Are you realy sure it is freed by calling Release if it is never calling
Hi Wilfried,
I have created an destructor Free, which inherited runs Free of
TWSocket. This
Free is never called; can anybody tell me why?
Are you realy sure it is freed by calling Release if it is never calling
Free?!
Regards,
Markus Mueller
> Hello Markus,
>
> you have to destroy it outside
Hello Markus,
you have to destroy it outside an event handler. to do that you can call
the Release method. Then it is destroyed when messages are pumped again,
so after your code finish.
---
Rgds, Wilfried [TeamICS]
http://www.overbyte.be/eng/overbyte/teamics.html
http://www.mestdagh.biz
Tuesday
Hello Mailinglist,
my project is now just working great, thanks very much for your
help... but there is just one question. Cause it only works fine
if I don't free TWSocket objects. If I Free them it often works
fine. But in much cases - for example - in the OnSessionClose
Handler (the memory of t
