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" "Black"
}
However, when the "MapWindowCurrentWorkSpace" directive from the config
file is processed, it calls WMapCreateCurrentBackGround() which loops
over all virtual screens, which (now) don't exist yet. So the settings
don't take effect.
The same problem occurs when WMapCreateDefaultBackGround() is called.
I tried simply moving the calls InitVirtualScreens() and
ConfigureWorkSpaceManager() back to where they were, but for some reason
that produces a core dump.
I suspect that the solution to be found would be splitting the
functionality of the calls to the 2 functions to a part to be done
before reading the config file, and a part afterward. But I don't know
how to perform this separation.
-Olaf.
--
___ Olaf 'Rhialto' Seibert -- You author it, and I'll reader it.
\X/ rhialto/at/xs4all.nl -- Cetero censeo "authored" delendum esse.
