Bugzilla – Full Text Bug Listing
| Summary: | Improper behavior for Model execution handler enablement. | ||
|---|---|---|---|
| Product: | [Modeling] AMP | Reporter: | Miles Parker <milesparker> |
| Component: | AXF UI | Assignee: | Jonas Ruttimann <jonas.ruettimann> |
| Status: | ASSIGNED --- | QA Contact: | Miles Parker <milesparker> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 0.9.0 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
All right. I'll will correct that behavior. (In reply to comment #0) > Recent changes have removed some model control behavior. It should be possible > to: > > a) Close a model that is currently running. (With new handler behavior you have > to stop it first.) Triggers transition {Active ->} Stopped -> Ending -> Ended. > b) Stop or close a model that is paused. > > Basically, we just want to save the users from unnecessary extra steps. I've refactored the Handlers and Commands and also all tests. Hope it's getting closer to what we want now. It seems to be working perfectly now as far as I can tell. Thanks! |
Recent changes have removed some model control behavior. It should be possible to: a) Close a model that is currently running. (With new handler behavior you have to stop it first.) Triggers transition {Active ->} Stopped -> Ending -> Ended. b) Stop or close a model that is paused. Basically, we just want to save the users from unnecessary extra steps.