lazarus/lcl/widgetset
2007-05-29 15:05:25 +00:00
..
README.txt
wsactnlist.pp
wsarrow.pp
wsbuttons.pp - tiny changes in non transparent speedbutton painting 2007-05-18 02:23:55 +00:00
wscalendar.pp
wschecklst.pp
wsclistbox.pp
wscomctrls.pp declared TListItem.Position, TListItem.Top, TListItem.Left with implementation for win32 (0008426) 2007-04-18 15:51:50 +00:00
wscontrols.pp BiDiMode patch from zaher dirkey (report 0008955) 2007-05-28 09:06:36 +00:00
wsdbctrls.pp
wsdbgrids.pp
wsdialogs.pp
wsdirsel.pp
wseditbtn.pp
wsextctrls.pp
wsextdlgs.pp
wsfilectrl.pp
wsforms.pp
wsgrids.pp
wsimglist.pp * Native imagelists - part 3 add&remove 2007-04-09 23:17:44 +00:00
wslclclasses.pp - fixed little bug in WS component reregistration (with new private) 2007-05-29 09:11:34 +00:00
wsmaskedit.pp
wsmenus.pp
wspairsplitter.pp - little behavior adjusting for non gtk pairsplitter 2007-05-29 15:05:25 +00:00
wsproc.pp * Native imagelists - part 3 add&remove 2007-04-09 23:17:44 +00:00
wsspin.pp LCL: - derived T(Float)SpinEdit from TCustomEdit to remove redundant code 2007-05-26 09:57:11 +00:00
wsstdctrls.pp - TCustomMemo.WantReturns implementation (0008352) 2007-05-10 14:12:03 +00:00
wstoolwin.pp

This directory contains all skeleton widget set component 
classes. These classes will never get instantiated and may 
only contain class functions.
  
=========  
IMPORTANT
=========  

Derivation and inheritance of classes is different then one
might be used to. It will be explained by the following 
examples.

Suppose the following LCL class hierarchy:

 TLCLComponent
     |
  TControl
     |
 TWinControl
 
the corresponding WS skeleton would be

 TWSLCLComponent
      |
  TWSControl
      |
 TWSWinControl


When method X of TWSControl gets implemented by 
widgetset Q the hierarchy looks like

 TWSLCLComponent
      |
  TWSControl.X --> TQWSControl.X
      |
 TWSWinControl


Calling TWSWinControl.X doesn't call TQWSControl.X since
it's parent is TWSControl. This problem is solved by 
modifying the class hierarchy at runtime.
When a component class is registered by RegisterWSComponent,
the class is copied and the vmt entries are adjusted so 
that the hierarchy looks like:


 TWSLCLComponent
      |
  TWSControl.X --> TQWSControl.X
                        |
                   TWSWinControl

In this case, calling TWSWinControl.X will call the overridden 
TQWSControl.X. The only thing which doesn't get handled is the 
inherited statement. Suppose there is also a TQWSWinControl.X 
which implements a few extra steps. In a normal situation one 
would have called "inherited". The call to inherited is
resolved at compile time and would in this example to a call to
TWSControl.X. That is not what we want.
To get around this, call the parent yourself:
  TWSWinControlClass(ClassParent).X