1. Using WS_BORDER in Windows XP
Anyone else notice the needless border that gets drawn around edit
controls, list views, tree views, etc. when using Win32Lib with XP?
Might I be so bold as to suggest that WS_BORDER be removed from all
controls as a default style?
Jonas Temple
http://www.yhti.net/~jktemple
2. Re: Using WS_BORDER in Windows XP
Jonas Temple wrote:
>
> Anyone else notice the needless border that gets drawn around edit
> controls, list views, tree views, etc. when using Win32Lib with XP?
I've fixed this for the next release.
> Might I be so bold as to suggest that WS_BORDER be removed from all
> controls as a default style?
I didn't go that far yet, as I no longer have a non-XP system to
test it on. But its a consideration for later on. I don't know why
original author(s) put WS_BORDER on these controls.
--
Derek Parnell
Melbourne, Australia
3. Re: Using WS_BORDER in Windows XP
Derek Parnell wrote:
>
> Jonas Temple wrote:
> >
> > Might I be so bold as to suggest that WS_BORDER be removed from all
> > controls as a default style?
>
> I didn't go that far yet, as I no longer have a non-XP system to
> test it on. But its a consideration for later on. I don't know why
> original author(s) put WS_BORDER on these controls.
It seems that WS_EX_CLIENTEDGE overrides WS_BORDER, at least on Win2K.
Most controls now seem to have this--maybe an archeologist out there
with some old Win32Lib can tell us what they used to have around the
v0.50 days (which was when I added the common controls).
It's probably safe to take WS_BORDER off as long as WX_EX_CLIENTEDGE
applies.
Matt Lewis
4. Re: Using WS_BORDER in Windows XP
> > I didn't go that far yet, as I no longer have a non-XP system to
> > test it on. But its a consideration for later on. I don't know why
> > original author(s) put WS_BORDER on these controls.
>
> It seems that WS_EX_CLIENTEDGE overrides WS_BORDER, at least on Win2K.
> Most controls now seem to have this--maybe an archeologist out there
> with some old Win32Lib can tell us what they used to have around the
> v0.50 days (which was when I added the common controls).
>
> It's probably safe to take WS_BORDER off as long as WX_EX_CLIENTEDGE
> applies.
WS_BORDER existed for most controls simply because Win32lib started out without
*any* _EX_ styles at all, and
WS_EX_CLIENTEDGE was simply 'overlaid' when it was first added.
Also should be remembered that Win32lib was originally running under a subsystem
3.0.10 exw.exe, which probably
influenced a lot of it's 'mucking-about' with various style flags.
