Re: can't bring "single instance" tray app to foreground
"Frank Cusack" <fcusack@fcusack.com> wrote in message
news:m2odiu9p9h.fsf@sucksless.local...
So I added a call at app startup to AllowSetForegroundWindow(ASFW_ANY),
which succeeds.
But adding MB_SETFOREGROUND to my dialog doesn't work.
MB_SETFOREGROUND should be used when calling MessageBox (or probably
AfxMessageBox too), not for a dialog. This is set in the dialog resource
editor, in the Properties view when the dialog form (and not any of its
controls) is selected. BTW, how were you adding MB_SETFOREGROUND to your
dialog??
But I am not
having the first instance bring the window to the top, I am having the
second instance do it itself.
How are you doing that? Since the first instance owns the dialog, it's the
one that needs to bring it to the top. Well, I've never called
::SetForegroundWindow(hwndOfAnotherProcess) before. Maybe it works, but
I've never done it.
Is it the case that a background app cannot bring itself to the
foreground? *Must* the second instance (I guess, the currently
foreground app) do this?
As long as the second instance (foreground app) calls
AllowSetForegroundWindow(), then the first instance can bring it's
window/dialog to the foreground. The concept is that only the app with the
foreground focus can give it away, by calling AllowSetForegroundWindow. Any
other process, including the first instance of your app, will be blocked
from having SetForegroundWindow() take effect... at least if the "foreground
lock timeout", a user setting, is enabled.
You may want to post your code, it may make it easier.
-- David