rose edit: multi-value field not marked as changed

[oliver-sanders]

If the value of a namelist entry has not been set and its meta type consists of multiple parts then when one changes the value in rose edit the field is not marked as changed.

Settup to replicate: app/foo/rose-app.conf

[namelist:bar]
baz=

app/foo/rose-meta.conf

[namelist:bar=baz]
type=real,real

[benfitzpatrick]

I think this is because we deliberately don't check validity or anything else until the whole 'row' has been filled in.

[oliver-sanders]

The reason that this is an issue is because of the way that rose edit attempts to 'fill in' values which are unset in a multi-part field. This is misleading as information is displayed which is valid but not set in the config.

In the above example the field will display as baz=0, 0 even though it is in-fact unset.

One solution to this problem would be to leave fields blank until there is user input as in the second screenshot (the first depicting the current behaviour).

Note: The default value for the python_boolean type would appear to be invalid at present.

Thoughts?