1. Toolbar and Statusbar
------=_NextPart_000_0058_01C0850C.CE2E0C80
charset="iso-8859-1"
Hi win32lib developers,
just a bit of advice.
I recommend that any toolbar and statusbar controls be created =
immediately after their parent window is created.
This is because these control types effect the location of the Client =
Area. And as the X,Y parameters on the create() function are relative to =
the client area, you could get "misplaced" controls if you create some =
before the toolbar/statusbar and some after the toolbar/statusbar.
Thanks to Judith for discovering this effect.
I suppose a workaround inside win32lib would be to automatically adjust =
the location of controls created before a toolbar/statusbar - but that =
just might cause other side-effects.
------
Derek Parnell
Melbourne, Australia
(Vote [1] The Cheshire Cat for Internet Mascot)
------=_NextPart_000_0058_01C0850C.CE2E0C80
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi win32lib developers,</FONT></DIV>
<DIV><FONT size=3D2>just a bit of advice.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>I recommend that any toolbar and statusbar controls =
be created=20
immediately after their parent window is created.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>This is because these control types effect the =
location of the=20
Client Area. And as the X,Y parameters on the create() function are =
relative to=20
the client area, you could get "misplaced" controls if you create some =
before=20
the toolbar/statusbar and some after the toolbar/statusbar.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>Thanks to Judith for discovering this =
effect.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>I suppose a workaround inside win32lib would be to=20
automatically adjust the location of controls created before a =
toolbar/statusbar=20
- but that just might cause other side-effects.</FONT></DIV>
<DIV><FONT size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>------<BR>Derek Parnell<BR>Melbourne,=20
Australia<BR>(Vote [1] The Cheshire Cat for Internet=20
------=_NextPart_000_0058_01C0850C.CE2E0C80--
2. Re: Toolbar and Statusbar
On Tue, 23 Jan 2001 07:19:21 +1100, Derek Parnell wrote:
>Hi win32lib developers,
>just a bit of advice.
>
>I recommend that any toolbar and statusbar controls be created immediately
after their parent window is created.
>
>This is because these control types effect the location of the Client
Area. And as the X,Y parameters on the create() function are relative to
the client area, you could get "misplaced" controls if you create some
before the toolbar/statusbar and some after the toolbar/statusbar.
>
>Thanks to Judith for discovering this effect.
>
>I suppose a workaround inside win32lib would be to automatically adjust
the location of controls created before a toolbar/statusbar - but that just
might cause other side-effects.
>
>------
>Derek Parnell
>Melbourne, Australia
>(Vote [1] The Cheshire Cat for Internet Mascot)
On a similar note, you cannot use 'setClientRect' on a window with a menu
before that window is drawn (e.g. if it's in your 'onOpen' routine). I've
found that it's height will end up being a menu-bar-size too short. (no
problem if it's used *after* your window is drawn.)
-- Brian
3. Re: Toolbar and Statusbar
On Tue, 23 Jan 2001 07:19:21 +1100, Derek Parnell <ddparnell at BIGPOND.COM>
wrote:
>Hi win32lib developers,
>just a bit of advice.
>
>I recommend that any toolbar and statusbar controls be created immediately
after their parent window is created.
>
>This is because these control types effect the location of the Client
Area. And as the X,Y parameters on the create() function are relative to
the client area, you could get "misplaced" controls if you create some
before the toolbar/statusbar and some after the toolbar/statusbar.
>
>Thanks to Judith for discovering this effect.
>
>I suppose a workaround inside win32lib would be to automatically adjust
the location of controls created before a toolbar/statusbar - but that just
might cause other side-effects.
>
>------
>Derek Parnell
>Melbourne, Australia
>(Vote [1] The Cheshire Cat for Internet Mascot)
>
>
4. Re: Toolbar and Statusbar
Note to IDE users. This affects you also until I can put a fix into the
module that creates the EXW file.
Judith
>On Tue, 23 Jan 2001 07:19:21 +1100, Derek Parnell <ddparnell at BIGPOND.COM>
>wrote:
>
>>Hi win32lib developers,
>>just a bit of advice.
>>
>>I recommend that any toolbar and statusbar controls be created immediately
>after their parent window is created.
>>
>>This is because these control types effect the location of the Client
>Area. And as the X,Y parameters on the create() function are relative to
>the client area, you could get "misplaced" controls if you create some
>before the toolbar/statusbar and some after the toolbar/statusbar.
>>
>>Thanks to Judith for discovering this effect.
>>
>>I suppose a workaround inside win32lib would be to automatically adjust
>the location of controls created before a toolbar/statusbar - but that just
>might cause other side-effects.
>>
>>------
>>Derek Parnell
>>Melbourne, Australia
>>(Vote [1] The Cheshire Cat for Internet Mascot)
>>
>>
