I ventured into some PBCC Windows programming.
Just a main window with some controls.
On WM_Create i install the controls, which works fine.
If i check this, WM_Create is sent exactly once.
When done i need to destroy some brushes and font handles (once). I initiated this from WM_Destroy.
To my surprise, when checking this, WM_Destroy is even for a fairly simple screen sent 36 to 39 times,
thus causing the cleanup to be done this number of times, which is a bit overdone.
Is there a true counterpart of WM_Create, which is sent exactly once if a thread finishes ?
Arie Verheul
Just a main window with some controls.
On WM_Create i install the controls, which works fine.
If i check this, WM_Create is sent exactly once.
When done i need to destroy some brushes and font handles (once). I initiated this from WM_Destroy.
To my surprise, when checking this, WM_Destroy is even for a fairly simple screen sent 36 to 39 times,
thus causing the cleanup to be done this number of times, which is a bit overdone.
Is there a true counterpart of WM_Create, which is sent exactly once if a thread finishes ?
Arie Verheul
Comment