New configurator backward compatibility

[krass]

looking at the way the config file is structured by [keyword] style sections I would expect a config file created on the new configurator to be backward compatible with any old firmware. [New sections] should either be meaningless to the old firmware and ignored; if not there would be a flood of very serious startup problem complaints, so I'm inferring from the lack of such complaints that it is, indeed, backwards compatible for the reason above.

The greying out then becomes a convenience and customer-interaction topic. it's poor to lead the customer into thinking he has to set an option_x that doesn't exist on his machine, but how does the Configurator know which firmware you have installed ? I'm not sure asking the customer to enter firmware version in the Configurator is a good model either, since there WILL be people who make errors.... probably best to do what they have done: one Configurator fits all.

I agree it's not perfect but they're treading new ground offering this in consumer hi-fi; maybe there's a better way to do this but possibly not with the current system architecture.