Xref: utzoo comp.os.vms:29084 comp.windows.x.motif:434
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!sol.ctr.columbia.edu!ursa!ari
From: ari@ursa.UUCP (Ari Rabinowitz)
Newsgroups: comp.os.vms,comp.windows.x.motif
Subject: Problems with DEC's Motif Window Manager for VMS
Message-ID: <6405@ursa.UUCP>
Date: 15 Aug 90 20:17:20 GMT
Reply-To: ari@ursa.UUCP ()
Organization: Bear Stearns, New York
Lines: 31


I am having a great deal of difficulty with the Motif window manager
supplied by DEC for VMS.  I was wondering if it is me, or MWM.EXE.

1) Although I have keyBoardFocusPolicy set to explicit, when I select a
DECTERM window, or almost any other DECWINDOWS client, (except LSE),
the pointer must be in the window (not on the border) for the window
to get keyboard focus.  The 'Active' border colors show that the window
is active, but keystrokes just go into the bit bucket.  I find this
particularly dangerous for my users, who constantly have people putting
papers on their desks and accidently moving their mice.  For this reason,
I am refusing to let my users use mwm, although management wants them to
for standardization reasons.

2) I would like to disable the f.kill function for DECTERMS, since closing
one terminal seems to kill the terminal emulator job, effectively killing
all of the existing terminal sessions.  I have tried many variations of
clientFunctions: -close
with no success.  Could someone tell me what, if anything will work for
this.  Also, wMenuButtonClick2: false does not seem to work for me.

3) Dec does not seem to have implemented the f.exec function for VMS,
which is something that I and my users would find to be of great value.
Does it work in some way I haven't found, or is it really not implemented?

Any help with all of this would be greatly appreciated.
Ari
-- 
Ari Rabinowitz		 	ari%ursa@ctr.columbia.edu
WorkStation Administrator	...!ctr.columbia.edu!ursa!ari
Bear Stearns