Home > Archive > Smartphone Developer Forum > March 2006 > Some weird problem with SetTimer(...) api
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Some weird problem with SetTimer(...) api
|
|
|
| in my main thread, I created a new thread, called A, in which I "postMessage"
to main thread a message, then Thread A exit.
the main thread got the message, and I called dialogbox(...), in its
DLGPROC, WM_INITDIALOG I called SetTimer(hwndDlg, ...), but the Wm_timer is
never received in my "DlgProc", although SetTimer return successfully.
the weird thing is when I use "SendMessage" instead, it works perfectly, but
which I don't like.
any suggestion??
| |
|
| Tim wrote:
> in my main thread, I created a new thread, called A, in which I "postMessage"
> to main thread a message, then Thread A exit.
>
> the main thread got the message, and I called dialogbox(...), in its
> DLGPROC, WM_INITDIALOG I called SetTimer(hwndDlg, ...), but the Wm_timer is
> never received in my "DlgProc", although SetTimer return successfully.
>
> the weird thing is when I use "SendMessage" instead, it works perfectly, but
> which I don't like.
whats thread A got to do with this? when you say postMessage you mean
PostThreadMessage()?
are you running your message pump in the thread that SetTimer is called in?
riki
----
No one should be able to patent something that could be designed by a
marketing department.-- some co-worker of Badgerman
By Night:
ThemeChanger for Smartphone : http://homepages.inspire.net.nz/~gambit/
AbstractStart for Smartphone :
http://homepages.inspire.net.nz/~gambit/AbstractStart/
Latest Betas have WM5 layout and speed dial support
|
|
|
|
|