extcap: Fix writing preferences to file

Do not change the preference pointer inside the Extcap Options
Dialog. That changes the real preference value, which disturbs
the check inside prefs_store_ext_multiple that storeValues() calls
for whether a pref has changed or not. Since the prefs are already
changed to their new value, we won't realize that we need to write
out a new preference file.

The other changes in #18487 are sufficent to fix the problem
identified there (though it's a bit unclear what "required" means
in combination with a default, and whether we have to send the
default value for the required parameter or can omit it.)

If the button says "Save", then save the preferences regardless
of what the "extcap Save on Start" preference says.

Fix #19639. Related to #18487

0 files changed, 0 insertions, 0 deletions