Some analysis on the InitVirtualScreens() function. It is doing too many
things at once.
For instance, it tries to establish if virtual screens should be used at
all - but does this incorrectly (or at least in a very weird way): the
variable userealroot is always True. But it also looks at the at
A few oddities regarding workspaces and captive ctwm windows:
- If you start a captive ctwm (ctwm -w) the new window will often move
off to some other workspace right away.
- If you use the WorkSpaceManager window inside the captive window, it
will not only switch the visible workspace inside
In revision f0b709dcd5269fb88b748a2e5d54e259d0f66881 on 2006-04-22, the
calls of InitVirtualScreens() and ConfigureWorkSpaceManager() were moved
after reading the configuration file.
MapWindowCurrentWorkSpace {
# border_color [background] [foreground] [bitmap]
"Red" "Yellow" "Blac
