Description
The unfoldedModel in odb is currently static — it reflects the database state at the time it was built and does not update when the underlying db is modified. Any changes to the db after the model is constructed leave the unfolded view stale, requiring manual rebuilds to stay consistent.
Suggested Solution
Extend dbChipCallBackObj with hooks for chip-structural mutations (dbChipInst, dbChipConn, dbChipBump, dbChipRegion, etc. — create/destroy and relevant modifications), then have unfoldedModel register a callback to incrementally update itself in response.
Description
The
unfoldedModelin odb is currently static — it reflects the database state at the time it was built and does not update when the underlying db is modified. Any changes to the db after the model is constructed leave the unfolded view stale, requiring manual rebuilds to stay consistent.Suggested Solution
Extend
dbChipCallBackObjwith hooks for chip-structural mutations (dbChipInst,dbChipConn,dbChipBump,dbChipRegion, etc. — create/destroy and relevant modifications), then haveunfoldedModelregister a callback to incrementally update itself in response.