form.closing

[Mickey Swanson]

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[pei_world]

what do you mean, are you trying to avoid form closing or what?
"Mickey Swanson" <sw*****@dixi e-net.com> wrote in message
news:uN******** ******@TK2MSFTN GP09.phx.gbl...

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[Mickey Swanson]

if a user clicks the x button I need to hide and minimize the form but I
can't just place this in the form.closing event because it will prevent
windows from shutting down. So I need to find out what is closing the form,
either a user or the operating system.

does that help describe what i'm looking for?
Mick
"pei_world" <pe*******@hotm ail.com> wrote in message
news:uc******** ********@TK2MSF TNGP12.phx.gbl. ..

what do you mean, are you trying to avoid form closing or what?
"Mickey Swanson" <sw*****@dixi e-net.com> wrote in message
news:uN******** ******@TK2MSFTN GP09.phx.gbl...

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[Rick Strahl [MVP]]

Hi Mickey,

No unforutnately not at least just using code in the Closing() event
handler. However, you can use WndProc to check for the system shutdown then
set a flag that the system is trying to shut down the app.

Something like this:

protected override void WndProc(ref Message m)
{
if (this.bNotifyIc on)
{
const int WM_QUERYENDSESS ION = 0x011;
if (m.Msg == WM_QUERYENDSESS ION)
this.bWindowsSh uttingDown = true;
}
base.WndProc(re f m);
}

In this case I use to trap the ShutDown event when the app is running in
NotifyIcon mode because usually when you shut down the form in that mode you
don't want to shut it down but minimize to the tray. The shut down message
however should need to be handled.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/webblog/
----------------------------------
Making waves on the Web
"Mickey Swanson" <sw*****@dixi e-net.com> wrote in message
news:uN******** ******@TK2MSFTN GP09.phx.gbl...

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[Mickey Swanson]

I've never used the WndProc. do you know where I can look at a more indepth
code sample.
Mick

"Rick Strahl [MVP]" <ri********@hot mail.com> wrote in message
news:eG******** ********@tk2msf tngp13.phx.gbl. ..

Hi Mickey,

No unforutnately not at least just using code in the Closing() event
handler. However, you can use WndProc to check for the system shutdown then set a flag that the system is trying to shut down the app.

Something like this:

protected override void WndProc(ref Message m)
{
if (this.bNotifyIc on)
{
const int WM_QUERYENDSESS ION = 0x011;
if (m.Msg == WM_QUERYENDSESS ION)
this.bWindowsSh uttingDown = true;
}
base.WndProc(re f m);
}

In this case I use to trap the ShutDown event when the app is running in
NotifyIcon mode because usually when you shut down the form in that mode you don't want to shut it down but minimize to the tray. The shut down message
however should need to be handled.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/webblog/
----------------------------------
Making waves on the Web
"Mickey Swanson" <sw*****@dixi e-net.com> wrote in message
news:uN******** ******@TK2MSFTN GP09.phx.gbl...

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[Mickey Swanson]

I think I understand. This is what I came up with.

protected override void WndProc(ref Message m)
{
const int WM_QUERYENDSESS ION = 0x011;
switch(m.Msg)
{
case WM_QUERYENDSESS ION:
this.bWindowsSh uttingDown = true;
break;
}
base.WndProc(re f m);
}

private void frmMDI_Closing( object sender,
System.Componen tModel.CancelEv entArgs e)
{
if(this.bWindow sShuttingDown)
{
Application.Exi t();
}
else
{
e.Cancel = true;
this.Hide();
this.WindowStat e = System.Windows. Forms.FormWindo wState.Minimize d;
}
}
"Rick Strahl [MVP]" <ri********@hot mail.com> wrote in message
news:eG******** ********@tk2msf tngp13.phx.gbl. ..

Hi Mickey,

No unforutnately not at least just using code in the Closing() event
handler. However, you can use WndProc to check for the system shutdown then set a flag that the system is trying to shut down the app.

Something like this:

protected override void WndProc(ref Message m)
{
if (this.bNotifyIc on)
{
const int WM_QUERYENDSESS ION = 0x011;
if (m.Msg == WM_QUERYENDSESS ION)
this.bWindowsSh uttingDown = true;
}
base.WndProc(re f m);
}

In this case I use to trap the ShutDown event when the app is running in
NotifyIcon mode because usually when you shut down the form in that mode you don't want to shut it down but minimize to the tray. The shut down message
however should need to be handled.

+++ Rick ---

--

Rick Strahl
West Wind Technologies
http://www.west-wind.com/
http://www.west-wind.com/webblog/
----------------------------------
Making waves on the Web
"Mickey Swanson" <sw*****@dixi e-net.com> wrote in message
news:uN******** ******@TK2MSFTN GP09.phx.gbl...

Is there any way to determing why a form is closing? As in if the user
cliced the x button or if a system shutdown has started.

thanks for any help
Mickey Swanson

[Jeffrey Tan[MSFT]]

Hi Mickey,

Yes, I think your code is correct. But I want to add more information to
you :) (For your original question about few information about WndProc)
WndProc encapsulated the win32 windows procedure. So you can override it
and handle certain message to do more indepth things.(When normal .Net
event does not meet your need)
To find the value of these message constant, you can look it up in the API
viewer followed with VB6.0.
To understand the message mechanism of windows application, I think the
best resource is some win32 SDK programming book. Such as "Programmin g
Windows" by Charles Petzold.

Hope this helps,

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Mickey Swanson]

Thanks, that helps alot.
I needed the tip on where to look up the constant values.
I also sent this to you directly by mistake. MS shouldn't put the Reply and
Reply Group button so close together. :-)
thanks,
Mick

""Jeffrey Tan[MSFT]"" <v-*****@online.mi crosoft.com> wrote in message
news:s9******** ******@cpmsftng xa07.phx.gbl...

Hi Mickey,

Yes, I think your code is correct. But I want to add more information to
you :) (For your original question about few information about WndProc)
WndProc encapsulated the win32 windows procedure. So you can override it
and handle certain message to do more indepth things.(When normal .Net
event does not meet your need)
To find the value of these message constant, you can look it up in the API
viewer followed with VB6.0.
To understand the message mechanism of windows application, I think the
best resource is some win32 SDK programming book. Such as "Programmin g
Windows" by Charles Petzold.

Hope this helps,

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

[Jeffrey Tan[MSFT]]

Hi Mickey,

Thanks for your feedback.
I am glad my reply makes sense to you.
Beside the API viewer, there are some windows const that was not normal
used. They are defined in the *.h files in the C:\Program Files\Microsoft
Visual Studio\VC98\Inc lude\ directory. So you can use the Edit|Find and
Replace|Find in Files menu in VS.net IDE.

Merry Christmas!

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.