[comp.os.vms] Problems with DEC's Motif Window Manager for VMS

ari@ursa.UUCP (Ari Rabinowitz) (08/16/90)

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 

mcmahon@tgv.com (John McMahon) (08/17/90)

In article <6405@ursa.UUCP>, ari@ursa.UUCP (Ari Rabinowitz) writes...
: 
: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.
:
:Ari Rabinowitz		 	ari%ursa@ctr.columbia.edu

Hmm...  I didn't know DEC was shipping MWM (or Motif anything) for VMS.  Can
someone provide details on availability, features, part numbers, etc ?

John 'Fast-Eddie' McMahon    :    MCMAHON@TGV.COM    : TTTTTTTTTTTTTTTTTTTTTTTT
TGV, Incorporated            :                       :    T   GGGGGGG  V     V
603 Mission Street           : HAVK (abha) Gur bayl  :    T  G          V   V
Santa Cruz, California 95060 : bcrengvat flfgrz gb   :    T  G    GGGG   V V
408-427-4366 or 800-TGV-3440 : or qrfgeblrq ol znvy  :    T   GGGGGGG     V

yee@osf.org (Michael K. Yee) (08/21/90)

In article <6405@ursa.UUCP> ari@ursa.UUCP (Ari Rabinowitz) writes:
>   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.
>   ...
	You're right.  This happens under Ultrix also.  This may be a bug
	with globally active windows.

>   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.

	This is a bug that has been fixed in Mwm 1.0.3.  I don't know if DEC
	has upgraded their VMS version of mwm.  If they have, then they have
	this fix.   The wMenuButtonClick2 resource works for me (on Ultrix).

>   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?

	Sound extremely useful to me too.

>   Ari

--
= Michael K. Yee =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
= OPEN Software Foundation -- 11 Cambridge Center -- Cambridge, MA 02142
= Phone: 617-621-8831      Email: yee@osf.org, uunet!osf.org!yee
= "I can't give you brains, but I can give you a diploma." -- The Wizard of OZ

murphy@ufp.dco.dec.com (Rick Murphy) (08/21/90)

Sorry to followup the followup, but the original question appears to have
expired on my news server..

In article <YEE.90Aug20150558@pmin27.osf.org>, yee@osf.org (Michael K. Yee)
writes:
|> In article <6405@ursa.UUCP> ari@ursa.UUCP (Ari Rabinowitz) writes:
|> >   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.
|> >   ...
|> 	You're right.  This happens under Ultrix also.  This may be a bug
|> 	with globally active windows.

I'm not having this problem, but I use 'pointer' keyboardFocusPolicy.

|> 
|> >   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.
|> 
|> 	This is a bug that has been fixed in Mwm 1.0.3.  I don't know if DEC
|> 	has upgraded their VMS version of mwm.  If they have, then they have
|> 	this fix.   The wMenuButtonClick2 resource works for me (on Ultrix).

Mwm.wMenuButtonClick2: false works for me, too.

|> 
|> >   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?
|> 

It's not implemented; Basically since the session manager starts the window
manager without a CLI. There's nothing available to run programs. (spawn won't
work..).

Send me mail if you want to have a look at my DECW$XDEFAULTS.
	-Rick

--
Rick Murphy, WA1SPT/4			Digital Customer Center, Landover, MD
Domain:  murphy@ufp.dco.dec.com -or- murphy@ufp.enet.dec.com
Bang:    decwrl!ufp.enet!murphy
Ding:	 (301) 306-2985
Disclaimer: This nonsense came from an AI program written in TECO. Ignore it.

mikey@eukanuba.wpd.sgi.com (Mike Yang) (08/21/90)

In article <6405@ursa.UUCP> ari@ursa.UUCP (Ari Rabinowitz) writes:
>   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.

In article <YEE.90Aug20150558@pmin27.osf.org>, yee@osf.org (Michael K.
Yee) writes:
|> 	You're right.  This happens under Ultrix also.  This may be a bug
|> 	with globally active windows.

Exactly.  Although DECwindows applications behave as "globally active"
clients as per the ICCCM, they use a pre-ICCCM protocol that only
DEC's window manager understands.  Therefore, MWM doesn't realize that
they're globally active.

DEC will probably release a new version of MWM in the future that will
correctly recognize old DECwindows clients and handle them accordingly.

-----------------------------------------------------------------------
                 Mike Yang        Silicon Graphics, Inc.
               mikey@sgi.com           415/335-1786

adrian@mti.mti.com (Adrian McCarthy) (08/21/90)

In article <6405@ursa.UUCP> ari@ursa.UUCP (Ari Rabinowitz) writes:
>   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.

I'm experiencing a minor annoyance, too.  The Close option in the menu you
get when you click the upper left corner of the window border seems to have
no effect on any applications (both DECwindows and Motif).  No error
message, nothing.  Do I have something configured incorrectly?

Aid.  (adrian@gonzo.mti.com)