RE: Customize buttons that change user's custom file should ask forconfirmation

[Drew Adams]

    Instead of "Erase Customizations":

        1) "Default Values" - resets to default (= installed) settings

        2) "Save" - the existing button. It would update the custom
           file to use the installed settings.

    This seems like a good idea.  Does anyone see a problem with it?

To clarify, in case it's not clear from this extract: require these two user
actions instead of the single Erase Customization action to get the same
effect.