Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!sdd.hp.com!spool.mu.edu!uunet!mcsun!ukc!servax0!sersun1!whisd
From: whisd@sersun1.essex.ac.uk (Whiteside S D B)
Newsgroups: comp.windows.ms.programmer
Subject: Static Windows and MoveWindow
Keywords: Static Windows, MoveWindow
Message-ID: <5194@servax0.essex.ac.uk>
Date: 22 May 91 09:34:33 GMT
Sender: news@servax0.essex.ac.uk
Reply-To: whisd@essex.ac.uk (Whiteside S D B)
Organization: University of Essex, Colchester, UK
Lines: 19

Can anyone help on this:

I create a static child window during my main window's WM_CREATE section.

I then size it properly when I get a WM_SIZE from Windows.

That all works okay. But then at another point I move the child window again, using MoveWindow. It removes the old static window, but doesn't repaint the new one. I do set the "redraw" field to TRUE.

However when I resize my parent window, the child window becomes visible again.

It seems that resizing the parent window sends extra messages that causes the static child to repaint itself which MoveWindow doesn't.

Can anyone suggest what's happening?

One a more general note: all this message passing seems highly confusing. It seems to go back on the idea that functions should have no side-effects. It's very hard to work out what's happening - what message begets what message etc.. Maybe it's just my first rude introduction to operating system-type programming. But it seems you have to do so much low-level type work to get even simple things to run.

Or am I talking to my grandmother about sucking eggs?

Simon Whiteside (WM_SIMON)