dce@smsc.sony.com (David Elliott) (10/19/90)
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.
yee@osf.org (Michael K. Yee) (10/25/90)
In article <1990Oct18.184714.12128@smsc.sony.com> dce@smsc.sony.com (David Elliott) writes: | | 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. There is a bug in the 1.1 Mwm app-defaults file. The setting of Mwm*windowMenu should be removed from Mwm.ad. This causes the problem you see where the user will get warnings about DefaultWindowMenu not being defined. The other (key and button) binding defaults should be OK. Your item 2 works for the key and buttons bindings, but not for the windowMenu. =Mike -- = Michael K. Yee -- yee@osf.org or uunet!osf.org!yee -- = OSF/Motif Senior SW Engineer = "I can't give you brains, but I can give you a diploma." -- The Wizard of OZ