Main-DB awars not saved if created in clients

[westram]

Example:

• open editor
• change search awars (e.g. 'probe region')
• save

⇒ changed search awars will not be saved

Most likely introduced by [8376]. merged into trunk with [8623]

[westram]

Possible solution:

• update temp-state of awar--entry on each change
  • con: if -entry changes (in a different way) state might be wrong (is that likely to happen?)
  • special handling for global awars needed?

[westram]

• fixed by [9744]
• behavior of global awars is confusing, but seems to be problem-free
  • sync is done via main-, but inside /tmp-branch, i.e. never gets saved anyway
  • global awars themselve are always members of properties- (awars in main- do not need to be declared as global since they ARE global as such)
    • global awars switch to tmp-state when set to default value (for [9744]) in server and client
    • saving properties in client with non-default value for such an awar, then setting awar back to default value in server, saving props there and restarting ARB works: local value of global awar in client gets overridden correctly