How to avoid use of timer when using TThread to communicate with UI thread?

You can post a message to the window in question. The timer works in a similar manner. It just fires off a windows message inside the form.

You obviously have a handle to the window CWnd::PostMessage(...) Don't use send message, it gets processed inline and could cause your thread to stop working Typically when you have a worker thread that attempts to access Guithread, they conflict. It's been a while since I've used MFC and threading but that's what I remember. I believe it's documented to work that way.

You can post a message to the window in question. The timer works in a similar manner. It just fires off a windows message inside the form.

You obviously have a handle to the window. CWnd::PostMessage(...) Don't use send message, it gets processed inline and could cause your thread to stop working. Typically when you have a worker thread that attempts to access Guithread, they conflict.It's been a while since I've used MFC and threading but that's what I remember.

I believe it's documented to work that way.

Builder5 uses VCL so it is a little different than MFC. – 0A0D Dec 8 '09 at 1:54.

I found the problem. I thought I was checking if my Form was null, but I was not. I fixed it making sure the form I was referencing is not null.

Edit: Turns out that one of the forms that is called when I call Fbutton1Click() is Modal so it blocks my thread. I ended having to go back to a timer to call the button click instead.. oh well.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.