Today I moved to a new workstation, so I got all the fun of setting up
new monitor and video card and all that fun X stuff. But post-move, a
minor ctwm issue showed up; calling f.occupy pulled up the occupy
window like normal, except I didn't see any buttons, and the window
was several dozen times as large as my screen in every direction. Um.
Whoops?
This tracks back to a few variables that are never initialized, unless
some options that I didn't know existed are in the config file.
Presumably it always got zero'd memory on my old system, so I never
noticed (and probably on most other people's systems, 'cuz otherwise
THEY'D have noticed). I've pushed a fix for it; attached is the
2-line patch in case anybody else runs into it.
--
Matthew Fuller (MF4839) | fulle...@over-yonder.net
Systems/Network Administrator | http://www.over-yonder.net/~fullermd/
On the Internet, nobody can hear you scream.
#
# old_revision [db710969dfa5d7225c4825c75aee971fb4572f8b]
#
# patch workmgr.c
# from [8ea886eb10be3f1bdf3ae7010f4eb36cbe9382c5]
#to [ea9dbcb2897548e5721e6a6cd2da57223c2dfaad]
#
--- workmgr.c 8ea886eb10be3f1bdf3ae7010f4eb36cbe9382c5
+++ workmgr.c ea9dbcb2897548e5721e6a6cd2da57223c2dfaad
@@ -143,6 +143,8 @@ void InitWorkSpaceManager (void)
Scr-workSpaceMgr.occupyWindow-geometry = NULL;
Scr-workSpaceMgr.occupyWindow-columns = 0;
Scr-workSpaceMgr.occupyWindow-twm_win = (TwmWindow*) 0;
+Scr-workSpaceMgr.occupyWindow-vspace= Scr-WMgrVertButtonIndent;
+Scr-workSpaceMgr.occupyWindow-hspace= Scr-WMgrHorizButtonIndent;
Scr-workSpaceMgr.curColors.back = Scr-Black;
Scr-workSpaceMgr.curColors.fore = Scr-White;