On Wed, 22 Nov 2017 17:48:34 +0000, Daniel James wrote:

> A window is a GUI abstraction that carries a lot of baggage (especially
> in Windows!) so a class that manages one is going to be big.
>
> I don't recall what OWL, in particular, did to split that up (I still
> have the manuals, somewhere ... and that was back in the day when
> manuals were well-written and thorough).

I'm actually supposing about OWL, because Borland Canada's back office
was very crumbly and never did deliver me the version of C++ that had OWL.
The split was that View supplied the base class for everything that would
appear on the screen, while Group instances handled all the messaging up
and down the parent-child tree.  Effectively all parents were Group
instances, and all View instances were children.  I don't remember the
details of my confusion, but I do recall having some trouble with the
different roles my objects wound up having under Windows OS.

 Mel.

--- SoupGate-Win32 v1.05