Install should not overwrite default key definitions (unless the user agrees to it)

[jbs]

Long-time users of the old default key definitions may find it very upsetting to discover that as a result of installing a new version of NEPMD (with the "new and improved" key definitions), the key strokes they are used to using no longer work in the same way. (Count me in this group!)

Presuming that any user's customized key definitions would already be kept intact, this ticket only applies to previous NEPMD users who do not have customized key definitions.

I propose that the install detect a preexisting NEPMD installation without any custom key definitions. If it detects such an installation, then either:

1) Automatically copy the old default key defs into the myepm subtree, making the old default keys a "custom" key definition for the new installation; or

2) Describe the new key defs to the user and ask if it is OK to install the new defs as the default. If the user agrees, then overwrite the previous default key defs. If the user does not agree, then follow option 1 above.

Either way the new key defs will be installed into the netlabs subtree giving the user the option to use the new key defs by backing out the previously-default-but-now-custom defs.

[Andreas Schnellbacher]

The CUA keyset 'cuakeys' is used as the default keyset. Activating the
old keyset is possible via the menu item

Options -> Keys -> Keyset additions

'cuakeys' must be changed to '-none-'.

1. Would another WarpIN install option be sufficient for you?

2. Exist there already too many WarpIN install options?

3. Another useful option to add would be stream/line mode. What do you think?

Andreas

[Andreas Schnellbacher]

Won't fix or not an additional bug. This was partly fixed by r2633.

There existed too many states with changing key and menu defs that were all not part of an official release. I guess the main confusion was because I changed the default keyset to cuakeys but also made it easy to switch back to the original keyset.

This is a missing documentation bug, for which a bug already exists: #1.

Andreas