Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!sdd.hp.com!caen!sol.ctr.columbia.edu!ira.uka.de!smurf!nadia!softpro!cmo
From: cmo@softpro.stgt.sub.org (Christian Motz)
Newsgroups: comp.unix.aix
Subject: Re: 3005 bugs
Message-ID: <146@softpro.stgt.sub.org>
Date: 18 May 91 12:10:15 GMT
References: <91137.082334DICKSNR@QUCDN.QueensU.CA>
Reply-To: cmo@softpro.stgt.sub.org (Christian Motz)
Organization: SOFTPRO, Software Professional GmbH, Boeblingen, Germany
Lines: 22

In article <91137.082334DICKSNR@QUCDN.QueensU.CA> DICKSNR@QUCDN.QueensU.CA (Ross M. Dickson) writes:
>
>Also, somewhat like the gentleman at Hypercube (Sorry, I've forgotten the name)
>I find that occasionally mwm "changes state" so that I've got to click
>on the window frame rather than the window in order to activate it.
>One time it even changed back after behaving that way for a few minutes.
>I've not been able to find anything I'm doing that correlates with this
>change of behaviour.

This sounds a lot like the behaviour that has always plagued the RISC's
implementation of X. Could it be that the window manager behaves "normal"
if you have NumLock off and starts acting up when you turn NumLock on?
I have experienced this problem from the beginning up to now (We are
currently running 3003, 3005 hasn't arrived yet).

Just my experiences, your mileage may vary.
                                                                 Chris.

-- 
SOFTPRO doesn't speak for me, and I do not speak for SOFTPRO. So what?

                              Christian Motz, cmo@softpro.stgt.sub.org