Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GUI: Fault tree construction #133

Closed
rakhimov opened this issue Jun 6, 2016 · 0 comments
Closed

GUI: Fault tree construction #133

rakhimov opened this issue Jun 6, 2016 · 0 comments

Comments

@rakhimov
Copy link
Owner

rakhimov commented Jun 6, 2016

No description provided.

@rakhimov rakhimov added this to the v0.12.0 milestone Jun 6, 2016
rakhimov added a commit that referenced this issue Jul 23, 2017
This is an implicit way to construct a fault tree in a model.
The approach does not allow fault-tree label modification.

Issue #133
rakhimov added a commit that referenced this issue Jul 23, 2017
Fault tree removals and additions are tracked by ModelTree.
ModelTree keeps the fault tree names sorted for usability and
so that the index does not have to be remembered by the undo actions.

Issue #133
rakhimov added a commit that referenced this issue Jul 25, 2017
Selected items are filled with color.

Issue #133
rakhimov added a commit that referenced this issue Jul 25, 2017
Upon double-click on digram events,
EventDialog opens up to allow editing.
The current implementation is not ideal
because it relies on the RAII dynamic_casts
to determine the appropriate dialog types.

Issue #133
rakhimov added a commit that referenced this issue Jul 26, 2017
The gate connective and arguments can be modified in the event dialog.
The modification tracking for the undo-stack is coarse
at formula level.
The whole formula is reset if any gate modification is made.

Issue #133
rakhimov added a commit that referenced this issue Jul 26, 2017
In EventDialog,
if an arg would introduce a cycle,
it is not added to the gate args list.
An explanation message is printed in the dialog.

The current implementation for cycle detection is not optimal.
It is exponential and based on descendants
rather than ancestors.
This is due to current limitations of the core API for mef::Event.

Issue #133
rakhimov added a commit that referenced this issue Jul 29, 2017
The diagram and tables are connected to the element id change signals.

Issue #133
rakhimov added a commit that referenced this issue Jul 30, 2017
Types can be changed for model events.

Constrains:
- Assumes normalized model
- Top gate type cannot be changed
- Basic and house events that are not in fault trees
  cannot be converted into gates.

The diagram is not yet connected to type change signals.

Issue #133
rakhimov added a commit that referenced this issue Jul 30, 2017
The events are not removable if there are dependents.

Issue #133
rakhimov added a commit that referenced this issue Jul 31, 2017
The fault tree removal is implicit upon the root gate removal.

Issue #133
rakhimov added a commit that referenced this issue Jul 31, 2017
The fault tree removal is implicit upon the root gate removal.

Issue #133
rakhimov added a commit that referenced this issue Jul 31, 2017
This is a crude implementation of the update
by redrawing the whole scene.

Issue #133
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant