'SAI/Create SAI using.../Max. frequency' broken

[westram]

Reproduce:

• start demo.arb
• select 'SAI/Create SAI using…/Max. frequency'
• enter "MAX_FREQUENCY" into input field (contains "none" in gtk, already contains "MAX_FREQUENCY" in motif)
• click "GO"

⇒ gtk-version creates an SAI called "none" (triggers problems described in #519). motif creates SAI "MAX_FREQUENCY" as expected.

This is a general problem:
gtk writes back the default value when some unknown value is written to an awar used in a selection list. This behavior does not comply with using an AWAR for a selection list and an input field (as done in the example above), i.e. providing some defaults in a list, while allowing the to enter a custom value.

Related tickets:

• #311 (not fixed - just vanished).
• #316 (fixed by [10107]; suspect?)
• #533
• #534

[westram]

Same in 'SAI/Create SAI using…/Consensus'

[epruesse]

The "default" value in selection lists is a bit of a broken API, IMO.

I don't have the details present right now, but I do remember that it took quite a few iterations to get this even half-way working. Different parts of ARB seem to expect idiosyncratic behavior of the old implementation.

Feel free to have a go at it, just be aware that things might break elsewhere if you change just about anything. Maybe you'll get it right.

Personally, I'm in favor of creating a new "" API that is more well defined in its behavior and fixing broken situations by moving to that. It's probably post-merge though.

[westram]

I just try to track down problematic cases and then use select_default_on_awar_mismatch(false); there

[westram]

by [12189] / [12190]

Solution: all creators of selection lists need to decide whether to use fallback2default or not

[westram]

Milestone powerusability deleted