OpenEuphoria

Re: [Win] ...two rules.

• Posted by Derek Parnell <ddparnell at BIGPOND.COM> Jan 25, 2001
• 474 views

Hi Wolf,

> The current definition for WS_OVERLAPPEDWINDOW in win32lib is wrong,

It has the same value as the Microsoft definition in Winuser.h

> Here's why it's wrong. ( my *emphasis* )

This does not mean it is "wrong", just a poor choice of coding style. As
WS_BORDER describes a specific look for window frames and WS_DLGFRAME
describes a different window frame look, one would normally assume that
these two styles are mutually exclusive. However, Microsoft has decided to
"reuse" these values by saying that if you *do* have both then it means
something else entirely different - namely that you want a title bar!

> Is WS_CLIPSIBLINGS ( I guess ) always a parent window default ?

Again, Microsoft in its wisdom has decided that if we create a window that
has child windows, that WS_CLIPSIBLINGS should be used. So therefore if we
don't specify it, Windows will add it in for us. I suspect that if we
actually don't want this style flag, we must explicitly remove the style
after the window has been created.

------
Derek Parnell
Melbourne, Australia
(Vote [1] The Cheshire Cat for Internet Mascot)