- OnCalculateLayout chooses to interpret a window's size and alignment. Therefore
- you
- could implement a different window class with a new OnCalculateLayout event
- handler,
- that has a more sophisticated way of laying out the windows. It might allow
- specification of whether stretching occurs in the specified orientation, for
- example,
- rather than always assuming stretching. (This could, and probably should, be
- added to the existing
- implementation).
-
- @e Note: wxLayoutAlgorithm has nothing to do with wxLayoutConstraints. It is an
- alternative
- way of specifying layouts for which the normal constraint system is unsuitable.
+ wxLayoutAlgorithm::OnCalculateLayout chooses to interpret a window's size and
+ alignment. Therefore you could implement a different window class with a new
+ wxLayoutAlgorithm::OnCalculateLayout event handler, that has a more sophisticated
+ way of laying out the windows. It might allow specification of whether stretching
+ occurs in the specified orientation, for example, rather than always assuming
+ stretching.
+ (This could, and probably should, be added to the existing implementation).
+
+ @note wxLayoutAlgorithm has nothing to do with wxLayoutConstraints.
+ It is an alternative way of specifying layouts for which the normal
+ constraint system is unsuitable.
+
+ @beginEventEmissionTable{wxQueryLayoutInfoEvent,wxCalculateLayoutEvent}
+ @event{EVT_QUERY_LAYOUT_INFO(func)}
+ Process a wxEVT_QUERY_LAYOUT_INFO event, to get size, orientation and
+ alignment from a window. See wxQueryLayoutInfoEvent.
+ @event{EVT_CALCULATE_LAYOUT(func)}
+ Process a wxEVT_CALCULATE_LAYOUT event, which asks the window to take a
+ 'bite' out of a rectangle provided by the algorithm. See wxCalculateLayoutEvent.
+ @endEventTable
+
+ Note that the algorithm object does not respond to events, but itself generates the
+ previous events in order to calculate window sizes.
+