The better mousetrap with a built-in trap

[Chris Botha]

If one wants to assure that there is only one instance of an app running,
then the popular solution is to use a Mutex and a message box, telling the
user there is already one running. I decided to go one further, bring the
1st instance to the foreground, no message boxes. Impressive, I thought. So
the first instance stores the main window handle in shared memory (win32
calls), second instance gets the window handle from shared memory if it
exists, and do a win32 "SetForegroundW indow" call. It works great if the
window is not minimized. Next step, when minimized, do a win32 "ShowWindow "
call. Also works great, BUT this is the trap in my mousetrap. If the main
form opened a dialog (ShowDialog), and the user minimizes the dialog, then
of course the main form minimizes too. Now start the second instance, it
finds the handle in shared memory and does a "ShowWindow " call, showing the
main window beautifully, however, the modal dialog stays minimized.
Naturally, the main form is dead, and the user has to click the dialog's
icon in the task bar to bring it up.
I don't really expect a solution, I thought I'd share my experience, and
revert back to the mutex and the message box.

[Bob Powell [MVP]]

Check out the Windows Forms Tips and Tricks page.

http://www.bobpowell.net/tipstricks.htm

--
Bob Powell [MVP]
Visual C#, System.Drawing

All you ever wanted to know about ListView custom drawing is in Well Formed.
http://www.bobpowell.net/currentissue.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm

Read my Blog at http://bobpowelldotnet.blogspot.com

"Chris Botha" <chris_s_botha@ AT_h.o.t.m.a.i. l.com> wrote in message
news:Oh******** ******@TK2MSFTN GP10.phx.gbl...

If one wants to assure that there is only one instance of an app running,
then the popular solution is to use a Mutex and a message box, telling the
user there is already one running. I decided to go one further, bring the
1st instance to the foreground, no message boxes. Impressive, I thought. So the first instance stores the main window handle in shared memory (win32
calls), second instance gets the window handle from shared memory if it
exists, and do a win32 "SetForegroundW indow" call. It works great if the
window is not minimized. Next step, when minimized, do a win32 "ShowWindow " call. Also works great, BUT this is the trap in my mousetrap. If the main
form opened a dialog (ShowDialog), and the user minimizes the dialog, then
of course the main form minimizes too. Now start the second instance, it
finds the handle in shared memory and does a "ShowWindow " call, showing the main window beautifully, however, the modal dialog stays minimized.
Naturally, the main form is dead, and the user has to click the dialog's
icon in the task bar to bring it up.
I don't really expect a solution, I thought I'd share my experience, and
revert back to the mutex and the message box.

[Chris Botha]

Bob, using "ShowWindowAsyn c" instead of "ShowWindow " was the key. Thanks.

"Bob Powell [MVP]" <bob@_spamkille r_bobpowell.net > wrote in message
news:uB******** *****@TK2MSFTNG P10.phx.gbl...

Check out the Windows Forms Tips and Tricks page.

http://www.bobpowell.net/tipstricks.htm

--
Bob Powell [MVP]
Visual C#, System.Drawing

All you ever wanted to know about ListView custom drawing is in Well Formed. http://www.bobpowell.net/currentissue.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm

Read my Blog at http://bobpowelldotnet.blogspot.com

"Chris Botha" <chris_s_botha@ AT_h.o.t.m.a.i. l.com> wrote in message
news:Oh******** ******@TK2MSFTN GP10.phx.gbl...

If one wants to assure that there is only one instance of an app running, then the popular solution is to use a Mutex and a message box, telling the user there is already one running. I decided to go one further, bring the 1st instance to the foreground, no message boxes. Impressive, I thought.

So

the first instance stores the main window handle in shared memory (win32
calls), second instance gets the window handle from shared memory if it
exists, and do a win32 "SetForegroundW indow" call. It works great if the
window is not minimized. Next step, when minimized, do a win32

"ShowWindow "

call. Also works great, BUT this is the trap in my mousetrap. If the main form opened a dialog (ShowDialog), and the user minimizes the dialog, then of course the main form minimizes too. Now start the second instance, it
finds the handle in shared memory and does a "ShowWindow " call, showing

the

main window beautifully, however, the modal dialog stays minimized.
Naturally, the main form is dead, and the user has to click the dialog's
icon in the task bar to bring it up.
I don't really expect a solution, I thought I'd share my experience, and
revert back to the mutex and the message box.

[Chris Botha]

Bob, there is a subtle bug in your single instance app code. The 2 lines
minimizing and restoring the form, use
ShowWindowAsync (RunningProcess es(0).MainWindo wHandle ...
Nine out of ten times it work, but then every now and then the original
instance occurs in
RunningProcesse s(1) and not RunningProcesse s(0), and testing for a null
handle and if so, use the second process in the array, fixes it.

"Bob Powell [MVP]" <bob@_spamkille r_bobpowell.net > wrote in message
news:uB******** *****@TK2MSFTNG P10.phx.gbl...

Check out the Windows Forms Tips and Tricks page.

http://www.bobpowell.net/tipstricks.htm

--
Bob Powell [MVP]
Visual C#, System.Drawing

All you ever wanted to know about ListView custom drawing is in Well Formed. http://www.bobpowell.net/currentissue.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm

Read my Blog at http://bobpowelldotnet.blogspot.com

"Chris Botha" <chris_s_botha@ AT_h.o.t.m.a.i. l.com> wrote in message
news:Oh******** ******@TK2MSFTN GP10.phx.gbl...

If one wants to assure that there is only one instance of an app running, then the popular solution is to use a Mutex and a message box, telling the user there is already one running. I decided to go one further, bring the 1st instance to the foreground, no message boxes. Impressive, I thought.

So

the first instance stores the main window handle in shared memory (win32
calls), second instance gets the window handle from shared memory if it
exists, and do a win32 "SetForegroundW indow" call. It works great if the
window is not minimized. Next step, when minimized, do a win32

"ShowWindow "

call. Also works great, BUT this is the trap in my mousetrap. If the main form opened a dialog (ShowDialog), and the user minimizes the dialog, then of course the main form minimizes too. Now start the second instance, it
finds the handle in shared memory and does a "ShowWindow " call, showing

the

main window beautifully, however, the modal dialog stays minimized.
Naturally, the main form is dead, and the user has to click the dialog's
icon in the task bar to bring it up.
I don't really expect a solution, I thought I'd share my experience, and
revert back to the mutex and the message box.

[Bob Powell [MVP]]

Hmm odd. Thaks I'll check up on that.

--
Bob Powell [MVP]
Visual C#, System.Drawing

All you ever wanted to know about ListView custom drawing is in Well Formed.
http://www.bobpowell.net/currentissue.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm

Read my Blog at http://bobpowelldotnet.blogspot.com

"Chris Botha" <chris_s_botha@ AT_h.o.t.m.a.i. l.com> wrote in message
news:uw******** ******@tk2msftn gp13.phx.gbl...

Bob, there is a subtle bug in your single instance app code. The 2 lines
minimizing and restoring the form, use
ShowWindowAsync (RunningProcess es(0).MainWindo wHandle ...
Nine out of ten times it work, but then every now and then the original
instance occurs in
RunningProcesse s(1) and not RunningProcesse s(0), and testing for a null
handle and if so, use the second process in the array, fixes it.

"Bob Powell [MVP]" <bob@_spamkille r_bobpowell.net > wrote in message
news:uB******** *****@TK2MSFTNG P10.phx.gbl...

Check out the Windows Forms Tips and Tricks page.

http://www.bobpowell.net/tipstricks.htm

--
Bob Powell [MVP]
Visual C#, System.Drawing

All you ever wanted to know about ListView custom drawing is in Well

Formed.

http://www.bobpowell.net/currentissue.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/gdiplus_faq.htm

Read my Blog at http://bobpowelldotnet.blogspot.com

"Chris Botha" <chris_s_botha@ AT_h.o.t.m.a.i. l.com> wrote in message
news:Oh******** ******@TK2MSFTN GP10.phx.gbl...

If one wants to assure that there is only one instance of an app running, then the popular solution is to use a Mutex and a message box, telling the user there is already one running. I decided to go one further, bring the 1st instance to the foreground, no message boxes. Impressive, I thought.

So

the first instance stores the main window handle in shared memory

(win32 calls), second instance gets the window handle from shared memory if it exists, and do a win32 "SetForegroundW indow" call. It works great if the window is not minimized. Next step, when minimized, do a win32

"ShowWindow "

call. Also works great, BUT this is the trap in my mousetrap. If the main form opened a dialog (ShowDialog), and the user minimizes the dialog, then of course the main form minimizes too. Now start the second instance, it finds the handle in shared memory and does a "ShowWindow " call, showing the

main window beautifully, however, the modal dialog stays minimized.
Naturally, the main form is dead, and the user has to click the

dialog's icon in the task bar to bring it up.
I don't really expect a solution, I thought I'd share my experience, and revert back to the mutex and the message box.