I've been having major problems trying to use the latest release (3.8.2) of CTWM on Xquartz.
I've now tried building it manually, and using the pre-built pkgsrc
binary, both with the same result.
My environment is XQuartz 2.7.7 (xorg-server 1.15.2) on Mac OS X 10.6.8
(it matters not where I've built and run CTWM though, of course, but I
did try just to be sure with a fresh build on a netbsd-current server,
and then running it as a remote app from the osx desktop)
I think this problem only affects XQuartz, though I've not yet really
properly tried any other server environment. If I get time to get it
working again I'll try X11 on one of my server boxes, and I suppose I
could try in a virtualbox VM too.
Anyway, what's happening is that some (not all) menus, e.g. the menu
I've defined for Button1 on the root window, will only appear in a fixed
location, and if the cursor isn't at the top-centre of that location
when you click, finding where to move the cursor to activate menu
selections is difficult/impossible (the active location for menu entries
is relative to where the menu should be, but there's no visual feedback
to know for sure you're over the right entry).
This happens only after the first use of the menu -- i.e. the fist time
I click Button1 on the root window the menu appears where it should,
i.e. where the cursor is modulo any offset required to keep the menu
visible, but subsequent times it appears where either it first did (and
for other menus it may be where the first-used Button1 menu appeared).
This first-use issue was the first clue and I finally got the next clue
after restarting CTWM enough times and realising that my menu would
re-appear the second time in the location where I had first activated
it.
The same problem happens for menus activated by window decorations
(e.g. RightTitleButton or LeftTitleButton). I.e. after first using such
a menu on one window and then trying to use it on another window it will
appear (as if) on the first window again!
So, for now I've just been sticking to an older release, 3.5.2, which
does not exhibit this problem. (twm doesn't have this problem either)
So, it seems that with Xquartz the location of the menu windows is being
stored and re-used for subsequent menu invocations (though some menus
appear to re-use the locations of other menus).
--
Greg A. Woods <[email protected]>
+1 250 762-7675 RoboHack <[email protected]>
Planix, Inc. <[email protected]> Avoncote Farm <[email protected]>
pgpvioRUywarm.pgp
Description: PGP signature
