Re: After EndDialog(...)

From: vipin (vipin_at_nospam.com)
Date: 04/30/04 

Date: Sat, 1 May 2004 03:24:51 +0530

Before I talk further, I will get back once I get a chance to diagnose a
problem remotely on one of the european locale win2ksp4 machines next week.
If I see this is indeed the problem I am gonna come back.

Till then bye
vipin

"Tim Robinson" <tim.at.gaat.freeserve.co.uk@invalid.com> wrote in message
news:c6ue32$ff9in$1@ID-103400.news.uni-berlin.de...
> vipin wrote:
> > My msdn also says the same thing and I know english to understand it.
> >
> > I don't think you are right. I find the dialog ended( atleast I don't
> > see it if I put a sleep(5000) after EndDialog(...) before the
> > DlgProc returns. This is in win2k sp4. I want to know whether the
> > call stack will be valid.
> >
> >
> > windows ---> DlgProc[ EndDialog(...) , DialogBox(....)]
>
> Sure, nothing touches the call stack. Even if EndDialog called
DestroyWindow
> straight away (which, according to MSDN, it doesn't), the call stack would
> be fine. (The stack only goes away if you exit the thread.)
>
> > Does windows still maintain the relation the intial "---->". What if
> > the same HWND is alloted to a new window ?
>
> Then you'd be referring to a different window when you thought you were
> referring to your own window.
>
> > something is missing in the msdn( some logical sequence????)
>
> I don't think there is.
>
> You could check this with Spy++. Run your program and set up a messages
> window on the dialog box itself. Set a breakpoint on the EndDialog call.
> Step over it and see what messages the dialog receives. If it's getting
> WM_DESTROY and WM_NCDESTROY then the dialog box is going away.
>
> --
> Tim Robinson (MVP, Windows SDK)
> http://mobius.sourceforge.net/
>
>

Relevant Pages

  • Re: After EndDialog(...)
    ... > My msdn also says the same thing and I know english to understand it. ... nothing touches the call stack. ... Then you'd be referring to a different window when you thought you were ...
    (microsoft.public.win32.programmer.ui)
  • Re: [RosAsm example]
    ... | using a CreateWindowEx() function call to create the main window, ... pop D$return;and reset stack for DefProc ... ;mov edx D$esp+020;whdl ...
    (alt.lang.asm)
  • minidump analysis
    ... A window asking to send error to Microsoft appears and a minidump is ... Only registers, stack and portions of memory are ... System Uptime: not available ... Symbol search path is: srv*c: ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Setting size limit of data while reading or writing from sockets
    ... the stack may wait for the application, ... With TCP, the available room in the socket receive buffer is ... Since he has no idea what window TCP advertises to the other end ... ... existing implementations *DO* shrink their windows. ...
    (comp.unix.programmer)
  • Re: minidump analysis
    ... > "Faulting application IPRRouting.exe, version 1.10.50.19217, faulting ... > A window asking to send error to Microsoft appears and a minidump is ... > Copyright Microsoft Corporation. ... Only registers, stack and portions of memory are ...
    (microsoft.public.dotnet.languages.csharp)