View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000507 | ascend | pygtk gui | public | 2011-04-12 00:39 | 2011-06-15 13:04 |
| Reporter | john | ||||
| Assigned To | |||||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Product Version | 0.9.7 | ||||
| Target Version | 1.0 | Fixed in Version | |||
| Summary | 0000507: propagate var/relation 'solved' status up through model hierarchy in processVarStatus | ||||
| Description | There is information from the solver that can be used to mark parts of a complex model solved, active or unsolved. This would help hugely with debugging, as one would quickly and visually be led to the part where solution has failed, and the variables which are causing problems. The idea would be to add more 'interface pointer' metadata to model instances, and to use that to add an icon next to the associated rows of the gtk.TreeView. One would need to do a depth-first traversal. A model containing only solved models, variables and relations could also be marked solved. A model containing and active models, variables and relations would always be marked active. All other models would be unsolved (ie the solver had yet reached that stage of the problem). Would need to think about how this works with conditional models. Might not be any different, not sure. | ||||
| Tags | No tags attached. | ||||
| related to | 0000423 | confirmed | Changing value of solved variable should force removal of 'solved' indication |
