🚀 go-pugleaf

"Remy Lebeau \(TeamB\)" <gambit47.no.spam@no.spam.yahoo.com> wrote:
>
>"JD" <nospam@nospam.com> wrote in message
>news:40ba78cc$1@newsgroups.borland.com...
>
>> As I said in my original post, I can't determine
>> the window state
>
> That is not what Bob is suggesting. Do not have the second
> instance try to detect the first instance's state.  Just
> have the second instance post a message to the first
> instance telling it what it needs to do, then have the
> first instance update its own state when needed.

I did that and it still didn't know what it's own state was.
As I stated in my original post, even from within the WndProc
method, the WindowState always evaluated to the last known
state PRIOR to being minimized.

Further, when I assumed it was minimized and restored it, I
had the problem with the minimize button.

>> - be it from ... within the WndProc of the first instance.
>
>Yes, you can determine the app's current state from within its own
>WndProc().

But it doesn't know. The WindowState *always* evalutes to the
last known state BEFORE it was minimized.

>An app always knows whether it is currently minimized or not.

But it doesn't. Not for Hans either.

~ JD