[sorry, I've not been otherwise occupied and not monitored closely enough and missed this]
> > Can somebody please explain to me (and to the manual page!) how virtual > > screens are supposed to work (conceptually)? What is their relation to > > workspaces? The manpage uses them as synonyms. Can I test them with > > captive windows? Can someone think about and reply to the comments I put > > in the CHANGES file? > > My understanding is that virtual screens support Xinerama. One head > is the one screen, the other head is the other screen. > > Most WMs do it so that a workspace spans all heads, so changing > workspace changes windows on all heads. > > I understood that the intent was for ctwm to do it differently: Here, > each workspace lives on a single head, so changing a workspace only > changes the windows on a single head. This is exactly it. It's uber useful for multi-headed display. The support Claude initially put in mostly worked, I just enhanced it a bit to handle restarts more gracefully, a few other assumptions being made about geometries for things off the main screen, as well as the ability to drag a window from one workspace to another and have it actually move. It's largely a virtualization of multiple X screens (:0.0, :0.1). Better than ripping it out would be to only call the virtualscreen funtionality if virtualscreens are enabled from the config file. I haven't checked the patch that was sent in, but will try to make some time to do so. -Todd
