[comp.windows.x] TWM bug

newton@cit-vax.Caltech.Edu (Mike Newton) (06/24/88)

Sorry this is to the net, but e-mail did not work.

I use twm a lot and like it very much.  Many thanks.  Unfortunately (how come
you only get praise when a fix is wanted?), I also have a nasty bug for you:

	When running 'uwm' or such on a Sun-3/60 that has a 'cgfour0' 
monitor, which has two different sets bit planes.  On these machines, 
there is in essenace two monitors, 'unix:0.0' and 'unix:0.1'.

	With uwm, i can start a window w/ -display unix:0.1 in the xterm
command line and it will show up on the alternate screen (found by
sliding the mouse off the edge, ie: the BW bit maps are used instead of
the color bitmaps, or vice-versa).  Twm does this too.

	However, with 'uwm', keyboard input goes to the correct place.  With
'twm'  all input in the 'alternate' window/bitlayers is lost.  So far the
only way i know of getting the input to the window is to pick it up with
the mouse (in the normal, 'front' layer) and lay it back down in the back
layer.

	Anyway, many thanks,

- mike

ps: the newer sun-3/60's may not always have the extra ram installed
for the B&W pixel layer.

ps: the devices that should exist are /dev/cgfour0 and /dev/fb.  NO
/dev/bwXXXXX exists.
-- 
newton@csvax.caltech.edu	amdahl!cit-vax!newton
Caltech 256-80			818-356-6771 (afternoons,nights)
Pasadena CA 91125		Beach Bums Anonymous, Pasadena President

	"Reality is a lie that hasn't been found out yet..."