: Saturday, July 18, 2009 3:44 AM
Subject: Re: [twsocket] [Fwd: Re: Conflicts between multiple instances]
Finally! A very simple bug causing very strange symptoms. I had overridden
Destroy in my ClientInstance object and neglected to include a final call
to the inherited Destroy.
Arno Garrels
Mike Lenox wrote:
Finally! A very simple bug causing very strange symptoms. I had
overridden Destroy in my ClientInstance object and neglected to
include a final call to the inherited Destroy.
I'm glad you solved it, good to know that it's not some bug with
ICS ;-)
--
Arno Garrels
Arno
I am aggressively debugging the application. The root problem at this
point seems to be a server background exception event. ICS sample code
has comments, Should normally never occur and Hoping that server will
still work. But, I am able to make it happen quite often and, though my
handler has
Mike Lenox wrote:
I am aggressively debugging the application. The root problem at this
point seems to be a server background exception event. ICS sample code
has comments, Should normally never occur and Hoping that server
will still work. But, I am able to make it happen quite often and,
Finally! A very simple bug causing very strange symptoms. I had
overridden Destroy in my ClientInstance object and neglected to include
a final call to the inherited Destroy.
Arno Garrels wrote:
Mike Lenox wrote:
I am aggressively debugging the application. The root problem at this
point
In my current app, I only have a main thread. So, does this, ...this
may cause a lot of trouble, apply? I should expect trouble if I have
multiple ICS components all executing on the main thread?
Original Message
Subject:Re: [twsocket] Conflicts between multiple
Is there a problem having multiple instances of ICS
socket objects on the same thread?
Defenitely no problem.
The most frequent error when using ICS components in a thread is to
forget
you must create the component from with the thread's execute method. If
you
create the component from
I guess I am not being very clear.
I am not creating other threads. I only have one ... the main Delphi thread.
I am creating different ICS components, a TTnCnx client and a
TWSocketServer in separate parts of my application. There are no shared
global variables and the two instances are in
Mike Lenox wrote:
BUT, the two objects seem to be interacting with each other as I get a
TTimer access error ONLY when both objects are active and I make an
actual connection to the server.
Both TWSocketServer and TTnCnx do not use a TTimer. If your code uses a
TTimer what is the event
I guess I am not being very clear.
Indeed...
I am not creating other threads. I only have one ... the main Delphi
thread.
Ah !
I am creating different ICS components, a TTnCnx client and a
TWSocketServer in separate parts of my application. There are no shared
global variables and the two
That's good information. I am not surprised if the TTimer is mine. BUT,
the issue is still that I only get the error when I have both ICS
components running. This implies that they are somehow interacting. Is
there any possibility of that or any past complaints of such behavior?
Arno Garrels
Mike Lenox wrote:
That's good information. I am not surprised if the TTimer is mine.
BUT, the issue is still that I only get the error when I have both ICS
components running. This implies that they are somehow interacting.
Why don't you debug the application? I guess an exception or access
12 matches
Mail list logo
