Re: Win32::GUI sending Windows messages between threads

[BrowserUk]

Use PostMessage() instead of SendMessage() and see how you fare?

[shadrack]

Same result with Postmessage (nothing happens).

A quick Google indicates the only difference between PostMessage and SendMessage is that PostMessage returns immediately while SendMessage waits for the recipient to process the message.

Anyway, I tried it. No difference.

[BrowserUk]

A quick Google indicates the only difference between PostMessage and SendMessage is that PostMessage returns immediately while SendMessage waits for the recipient to process the message.

You are correct, but you have missed the significance.

1. SendMessage is a synchronous call.

   If the timer handler -- your custom function -- takes a long time to run, it will cause your GUI to freeze until it is finished.

2. PostMessage() is an asynchronous call;

   The message is added to the queue and processed when it reaches the top. This allowing the originator of the message to do other things during the interim.

[Anonymous Monk]

My point was that the difference did not seem to be relevant to the fundamental problem that nothing seems to happen when I call SendMessage(). As I said, I tried it and nothing happened with PostMessage() either. If neither solves my problem, the difference is academic.

... or am I missing something?

[shadrack]

I can't seem to reply to your last message for some reason, but I am aware of the timer ID issue and I did try several different values for wParam and lParam even before my initial post. None of them seemed to be any more effective than using 0, 0, and some even blew up perl, so I left them out of the example. Anyway, I solved the problem by using a different message all together (WM_USER) as is (now) detailed in the OP. Thx.