Andreas Mohr [EMAIL PROTECTED] writes:
Windows definitely does NOT do it this way, of course
(well, I'd be surprised if it actually did ;-).
This is just a (crude, if you want) hack to make it work.
And I figured sending WM_NULL shouldn't hurt.
That's in the "famous last words" category...
On Mon, Feb 05, 2001 at 02:10:21PM +0100, gerard patel wrote:
At 08:52 PM 30/1/01 +0100, you (Andreas Mohr) wrote:
snip
Just send WM_NULL to unblock the dialog's message loop after setting DF_END.
I can't see this WM_NULL with Winsight. Maybe it's a bug in
Winsight :-/, but are you sure
At 10:37 AM 5/2/01 -0600, you wrote:
I can't see this WM_NULL with Winsight. Maybe it's a bug in
Winsight :-/, but are you sure it's not some framework that is
sending it ?
Hmm, what are you talking about ?
And I don't quite understand what you're investigating here... ;-)
*I* don't
On Mon, Feb 05, 2001 at 09:24:42PM +0100, gerard patel wrote:
At 10:37 AM 5/2/01 -0600, you wrote:
I can't see this WM_NULL with Winsight. Maybe it's a bug in
Winsight :-/, but are you sure it's not some framework that is
sending it ?
Hmm, what are you talking about ?
And I don't
At 02:38 PM 5/2/01 -0600, you wrote:
Well, examining how Windows does it can be done,
but I don't think it's too useful, as I think that the current approach
with that fix should work fine.
Now I think I see : this can only be useful if EndDialog is called from
another thread, right ? If yes,
