Opened 10 years ago

Closed 10 years ago

#266 closed defect (fixed)

Main-DB awars not saved if created in clients

Reported by: westram Owned by: westram
Priority: critical Milestone:
Component: Library (GUI) Version:
Keywords: Cc:

Description

Example:

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

⇒ changed search awars will not be saved

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

Change History (2)

comment:1 Changed 10 years ago by westram

  • Status changed from new to assigned

Possible solution:

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

comment:2 Changed 10 years ago by westram

  • Resolution set to fixed
  • Status changed from assigned to closed
  • fixed by [9744]
  • behavior of global awars is confusing, but seems to be problem-free
    • sync is done via main-DB, but inside /tmp-branch, i.e. never gets saved anyway
    • global awars themselve are always members of properties-DB (awars in main-DB 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
Note: See TracTickets for help on using tickets.