Ticket #838 (closed assessed: fixed)
Core variable adjustments do not dirty the database
| Reported by: | chiarap | Owned by: | jeroens |
|---|---|---|---|
| Priority: | normal | Milestone: | Ecopath 6: release 6.2 |
| Component: | Overall Plugins | Version: | |
| Severity: | tweak | Keywords: | save |
| Cc: |
Description
When the core prompts for core values to be changed, such as Diet not summing to one or Biomass Accumulation corrections, the 'save as' button does not get enabled.
Change History
comment:2 Changed 12 years ago by jeroens
Just to clarify: when the core DIRECTLY alters variables these changes bypass the regular Validation scheme and cCore.OnValidated? / cCore.OnChanged?. This may need to change.
comment:3 Changed 12 years ago by jeroens
BIG QUESTION: Should this also apply to estimated variables, i.e. should estimations for input variables cause the database to be flagged as dirty?
comment:4 Changed 12 years ago by jeroens
- Status changed from new to closed
- Resolution set to fixed
Talked to VC: whenever input variables are changed by the user or the core, the dirty prompt should appear and the database can be saved.
Implemented this for BA, Immig and Emig, Diet. There may be other cases, but these are the most important variables that needed dealing with
The data source does not get 'dirty' triggers when the core alters variables.