Hmmm.. that's really weird... a textbox being R/O or not, this has
absolutely nothing to do with threading.
Here's another suggestion - replace BeginInvoke with Invoke. Updating the
textbox' contents should be quick, so I think it is OK if the worker thread
stops and waits while the textbox' value is updated.
If the problem persists, try a profiler (I recall there was a freeware one).
> Hi Dmytro,
>
[quoted text clipped - 76 lines]
>> > Any help would be appreciated, thank-you in advance
>> > Am I missing something with the thread?
Leo W. - 24 May 2006 09:04 GMT
> Here's another suggestion - replace BeginInvoke with Invoke. Updating the
> textbox' contents should be quick, so I think it is OK if the worker thread
> stops and waits while the textbox' value is updated.
I'll try this thanks for the suggestion.
A little further update, I have been testing it today, and...
1. If I DO NOT click inside the text box (Any of the textboxes that I have
updated in the second thread, using the begin.invoke the program works ok, so
far)
2. If I click in ANY of the textboxes (That were updated in the thread),
then the program goes un-responsive.
I'll try your suggestion and let you know.
Thanks, Leo
> If the problem persists, try a profiler (I recall there was a freeware one).
>
[quoted text clipped - 78 lines]
> >> > Any help would be appreciated, thank-you in advance
> >> > Am I missing something with the thread?