Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x.motif
Subject: Motif 1.1 mwm default bindings problem
Message-ID: <1990Oct18.184714.12128@smsc.sony.com>
Date: 18 Oct 90 18:47:14 GMT
Sender: dce@smsc.sony.com (David Elliott)
Organization: Sony Microsystems Corp, San Jose, CA
Lines: 32


In Motif 1.0, the mwm app-defaults file didn't set any of the bindings
resources.  This meant that new users used the builtin defaults, and
not the buttons, keys, and menus defined in the system.twmrc file.

In Motif 1.1, the mwm app-defaults file sets the following resources:

	Mwm*buttonBindings:		DefaultButtonBindings
	Mwm*keyBindings:		DefaultKeyBindings
	Mwm*windowMenu:			DefaultWindowMenu

This is nice for new users, since it means they use the system.twmrc
items.

But, people who used the builtin default values in Motif 1.0 and
switched to Motif 1.1 now get warning messages about DefaultWindowMenu
not being defined.  Even worse, mwm doesn't fall back on the default,
so the menus aren't defined at all.

It seems to me that there are three courses of action:

	1. Don't set the bindings in the app-defaults file. (This
	   is my temporary solution.)

	2. Change mwm so that if a binding can't be found it
	   falls back on the builtin default.

	3. Let the users fix their .mwmrc files.

I think that 1 hurts new users and 3 is not a good idea, since not all
users who have their own .mwmrc files really know enough to fix the
problem.