Steve,

No problem - I still don't know what some of the options do - or are supposed 
to do, but I'll document what I can. It's a start at least:)

Cheers,

jez.
  ----- Original Message ----- 
  From: Stephen Pick 
  To: Jez White ; Win32-GUI 
  Sent: Monday, January 19, 2004 10:00 AM
  Subject: RE: [perl-win32-gui-users] Rebar take 3


  Hi Jez,

  I'm in the process of adding all the missing documentation in Win32::GUI. 
I've documented well over 50 methods that were previously undocumented. If you 
find any quirks in the Rebar or would like to document some bits of it for me, 
that would be very helpful, since I've never attempted to use it I'm not the 
best person to document it.

  Steve
    -----Original Message-----
    From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Jez White
    Sent: 19 January 2004 09:55
    To: Win32-GUI
    Subject: [perl-win32-gui-users] Rebar take 3


    Hi,

    For those who don't know what a rebar (sometimes called "coolbar") control 
is:

    It's basically like a tool bar that allows you to create bands where you 
can attach other controls or child windows. You can move these bands around. 
Rebar controls are used in a lot of applications, such as word processors where 
you might have the current style or font in a dropdowns in the "tool bar".

    
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/shellcc/platform/commctls/rebar/rebar.asp

    The rebar control is badly documented in win32::gui, and has various 
methods/functions missing and I suspect a couple of bugs - but the control 
works quite well. The example below, contains a rebar control with three bands. 
Two of the bands contain a child window. Each child window contains several 
controls (dropdowns, datetime and buttons). With the Steve's scroll bar example 
of a few days ago I have changed the way child windows are created, so they now 
act correctly (they do not take focus away from the main window). I assume that 
this is the correct approach?

    In the next couple of days I'll try and find out what 
methods/functions/events are missing, as well as identify any bugs and create 
the relevant tracker items. I would be grateful for feed back on this example.

    Cheers,

    jez.






Reply via email to