run at shutdown ...
-
The problem with the
WM_QUERYENDSESSIONmessage is that an application can return 0 in response to it and Windows will not shut down.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
Exactly what he may need if he want to do some processing and then call the ExitWindow family of API Papa while (TRUE) Papa.WillLove ( Bebe ) ;
If, during the processing of the
WM_QUERYENDSESSIONmessage, a call is made toExitWindows[Ex](), does that not re-send theWM_QUERYENDSESSIONmessage? As I read Alex's original post, he was interested in doing something if Windows was shutting down, not if Windows was asked to be shut down. If work was done during the processing ofWM_QUERYENDSESSION, it is not guaranteed that Windows will shut down, thus the processing may be immature.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
If, during the processing of the
WM_QUERYENDSESSIONmessage, a call is made toExitWindows[Ex](), does that not re-send theWM_QUERYENDSESSIONmessage? As I read Alex's original post, he was interested in doing something if Windows was shutting down, not if Windows was asked to be shut down. If work was done during the processing ofWM_QUERYENDSESSION, it is not guaranteed that Windows will shut down, thus the processing may be immature.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
Alex HexR wrote: ...although application should be whole time in memory. Which is not what you indicated in your original post. "There is no reason to keep it during whole session in memory" is not the same as "although application should be whole time in memory." Alex HexR wrote: not a big deal, dos times are over and we have enough memory This make no sense whatsoever. What does DOS and enough memory have to do with your post or my reply? You wanted to know when Windows was shutting down so that you could check some things.
WM_ENDSESSIONis the message you'll need to handle to know that Windows is shutting down.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
DavidCrow wrote: dos times are over "dos" -> "those", methinks. :) /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com
I'm unclear on your intent here as none of my posts in this thread mentioned anything about "dos times are over."
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
I'm unclear on your intent here as none of my posts in this thread mentioned anything about "dos times are over."
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
I was referring to Alex's post. I think he meant "those times are over", where as you interpreted his misspelling as having to do with DOS. /ravi My new year's resolution: 2048 x 1536 Home | Articles | Freeware | Music ravib@ravib.com
Nothing was misspelled. He clearly meant DOS.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
Nothing was misspelled. He clearly meant DOS.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
Ravi Bhavnani wrote: We're both talking about this msg[^], right? Correct.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
-
If, during the processing of the
WM_QUERYENDSESSIONmessage, a call is made toExitWindows[Ex](), does that not re-send theWM_QUERYENDSESSIONmessage? As I read Alex's original post, he was interested in doing something if Windows was shutting down, not if Windows was asked to be shut down. If work was done during the processing ofWM_QUERYENDSESSION, it is not guaranteed that Windows will shut down, thus the processing may be immature.
"The pointy end goes in the other man." - Antonio Banderas (Zorro, 1998)
so, as i understand Alex's question (or even if it is not his, it's mine :-D), is there a way to lauch a program which is not executing when windows shuts down (and so don't use memory for nothing - because it is not needed before the loggout) ? the problem is, when you catch the
WM_ENDSESSION, the program must be currently running to catch the event...
TOXCCT >>> GEII power
