Re:Sending a window a WM_DESTROY is like prank calling prete...
by molo_ on Wednesday September 28, 2011 @11:47AM
(#3048454)
This is about an OS-layer API, not a windowing toolkit API. Tying the window to a thread at this layer makes it impossible to have a single-threaded UI application. It is inflexible.
[ Parent
| on HN ]
Re:Sending a window a WM_DESTROY is like prank calling prete...
by roel_v on Wednesday September 28, 2011 @05:46PM
(#3050056)
"This is about an OS-layer API, not a windowing toolkit API"
What does that even mean? Of course you can have single-threaded UI applications in Windows, the majority of them are. Have you ever written a Windows application in C or C++?
Re:Sending a window a WM_DESTROY is like prank calling prete...
by to3m on Wednesday September 28, 2011 @12:13PM
(#3048592)
What exactly is the problem with the approach?
Re:Sending a window a WM_DESTROY is like prank calling prete...
by innes on Wednesday September 28, 2011 @04:03PM
(#3049625)
Sorry. I've read your comment a couple of times and am unable to make any sense of it. Win32 is a (dated, clunky) API for writing GUIs (in part). "OS-layer" is babble in this context.
And yeah, i would stop signing your posts - it comes across as conceited somehow; like each comment is a big deal.