On Tue, Feb 18, 2003 at 11:11:54PM +0100, Per Olofsson wrote: > Hmm... so screens have a big flat list of _all_ objects that are on > the screen. And the hierarchy lies in the implementation-specific > lists defined in the manager objects. But then each object has an > attribute that specifies which manager it is managed by, if any?
Screens only list all the objects corresponding to windows that are children of the root window and the objects managing these windows (workspaces). Client windows (or nested frames etc.) and such are not on the screen's list unless in full screen mode. > When you're talking about PWM "workspaces", are you referring to an > Ion workspace that works like a PWM workspace or are you talking in > more general terms about an object that can manage windows as PWM > does? A new (simple) object that doesn't place restrictions on the geometries of the managed objects (unlike WWorkspace's tiling/splitting does). And yes, such and object could be put inside a frame like WWorkspaces and almost everything can (at least in theory) be put. -- Tuomo
