Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

DSDP/MTJ/Remove Event

< DSDP‎ | MTJ

Use-Case Specification: Remove Event


1. BRIEF DESCRIPTION

The user removes an event from the selected component.


2. FLOW OF EVENTS

2.1 Basic Flow of Events

B1. The user decides to remove an event from the selected component.
B2. The user opens the event list for the selected component.
B3. The user selects the event to remove.
a) The system removes the event-related code. This contains the event’s code and all of the code that was added to the components to make them listen to the event.
b) The system removes the event from the UI designer.

2.2 Alternative flows

Alternative flow 1: The user removes the event from the code in the code editor
A1. If the user removes the event in the code editor, the system notices that the code has been changed and re-parses the code for design. This effectively removes the event from the UI designer.
Alternative flow 2: The code file cannot be opened
A2. If the system cannot open the code file for editing, the user will be warned about the error and the removal is cancelled.


3. SUBFLOWS


4. KEY SCENARIOS


5. PRECONDITIONS

5.1 The UI designer is open and includes a component that has at least one event
Events can only be removed from components in the UI designer.


6. POSTCONDITIONS

6.1 Postcondition 1
The event is removed from the UI designer’s design and the event’s code is removed

6.2 Postcondition 2: The undo feature is available
The undo feature allows the user to undo the removal of the event.


7. EXTENSION POINTS


8. SPECIAL REQUIREMENTS


9. ADDITIONAL INFORMATION



Comments:


Back to main DSDP-MTJ Use Cases

Back to the top