RE: Problem writing Configs back to xPLHal

[Tony Tofts]

> Might be useful for hardware based devices with none/limited
> Non-Volatile-Memory, all they would need to set/store was
> their sourceID the rest could be provided via Xpl.

That's what it does now, but it's assumed the device doesn't change it's
own
values - only loads defaults. All changes are expected via xpl config
messages

In fact changing the config values once the ocx is active is not a good
idea.
By doing this it overwrites the default values used when resetting.
E.g. if a config is sent to the device like filter=
This is taken to mean restore defaults, i.e. the values loaded at startup,
but if the app has changed the config values these become the defaults...

> It would
> also act as a backup mechanism for devices or applications.
> If an app or hardware device died and the local dynamic data
> went too, you could recover it from the .cfg file in xplHal.

In theory no device/app needs to store any local data (that relates to a
config item) xplhal (or any config manager) can supply them all.

Regards
Tony