 |
BorlandTalk.com Borland discussion newsgroups
|
| View previous topic :: View next topic |
| Author |
Message |
qyte Guest
|
Posted: Mon Apr 25, 2005 11:34 am Post subject: TIdTCP problem. |
|
|
i have the following problem and cannot figure out
what maybe causing it.
the problem exists in either the client or the server
side of the app.
when i read something from the connection
i put in a memo inside form2.
form2 is invisible in the beginning.
if a string comes i show form2 and the
add the string to the memo.
the problem is that the whole application freezes.
that problem does not exist if i have
already pressed a button to make the form2
visible. what i mean is that if form2 is
visible from the begging there is no problem.
i tried using the bcb debugger and the was an exception
like "Canvas could not be drawn" or something like that.
Can anyone tell me what is the problem in this case?
|
|
| Back to top |
|
 |
Remy Lebeau (TeamB) Guest
|
Posted: Mon Apr 25, 2005 4:50 pm Post subject: Re: TIdTCP problem. |
|
|
"qyte" <gyte (AT) vivodinet (DOT) gr> wrote
| Quote: | when i read something from the connection
i put in a memo inside form2.
|
Please show that code. If you are doing that from a server, than are you
synchronizing it properly? Indy servers are multi-threaded. You should not
be accessing the GUI directly while inside a thread-based event handler.
| Quote: | the problem is that the whole application freezes.
|
Again, please show your actual code.
| Quote: | i tried using the bcb debugger and the was an exception
like "Canvas could not be drawn" or something like that.
|
That usually occurs from thread-unsafe access to the GUI.
Gambit
|
|
| Back to top |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|