Inconsistencies in `SettingsEvent`

[david-strahl]

The list of change parameters is relative to the initial values (or last submitted) for submitting and resetting. For changing a value, the changed parameter is always the one that triggered the event even when the new value is the same as in the initial value set.

Maybe better to be relative to the last dispatched event.

[david-strahl]

Be more clear about when an event is dispatched:

• settings-changed: Dispatched when the input value changes, holding only this parameter in the changed list.
• settings-submit: Dispatched when the submit button is clicked, holding a list of all parameters that are different to the last submit event for changed.
• settings-reset: Dispatched when the settings are reset, but only when there is a value that changes with resetting.

[david-strahl]

How does the Settings Form know, from where it was opened?

Should this be known? Maybe it is better if the user needs to remember what settings were used to open the form.

[david-strahl]

All changed parameter names are now relative to the latest submitted values.