Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 350997 - Improper behavior for Model execution handler enablement.
Summary: Improper behavior for Model execution handler enablement.
Status: ASSIGNED
Alias: None
Product: AMP
Classification: Modeling
Component: AXF UI (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Jonas Ruttimann CLA
QA Contact: Miles Parker CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-02 15:35 EDT by Miles Parker CLA
Modified: 2011-07-26 14:27 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2011-07-02 15:35:31 EDT 
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.
Comment 1 Jonas Ruttimann CLA 2011-07-04 01:26:06 EDT 
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.
Comment 2 Jonas Ruttimann CLA 2011-07-04 11:23:21 EDT 
I've refactored the Handlers and Commands and also all tests. Hope it's getting closer to what we want now.
Comment 3 Miles Parker CLA 2011-07-26 14:27:09 EDT 
It seems to be working perfectly now as far as I can tell. Thanks!