-
Notifications
You must be signed in to change notification settings - Fork 51
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
Refactored crosscut functionality. #684
Conversation
kecso
commented
Nov 18, 2015
- connections now visualized like in Composition view
- set membership relation is visible
- relations can be filtered on every crosscut
- filter states are saved with the project
- default connection manager is set to CM2
- manual tests have been created and stored on google drive
- if a node is visualized as port and as a separate item as well the preference is at the item (so connections will end there)
- adding a node to the crosscut if it was already visualized as port is now possible (both become be visible)
- removing a node that is also visualized as port is now possible
- connections now visualized like in Composition view - set membership relation is visible - relations can be filtered on every crosscut - filter states are saved with the project - default connection manager is set to CM2 - manual tests have been created and stored on google drive - if a node is visualized as port and as a separate item as well the preference is at the item (so connections will end there) - adding a node to the crosscut if it was already visualized as port is now possible (both become be visible) - removing a node that is also visualized as port is now possible
@@ -1808,6 +1868,7 @@ define(['js/logger', | |||
this._GMEID2ComponentID[gmeID].push(uiComponent.id); | |||
this._ComponentID2GMEID[uiComponent.id] = gmeID; | |||
|
|||
this._delayedConnectionsAsItems = this._delayedConnectionsAsItems || {}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couldn't this property be defined in the constructor? Is it declared here too? Or is it set to null at some point?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you are right, it should be in the constructor (or actually in the initialization of the tab...)
See #668 regarding using CM2.. |
I'll check the tests again with AR and remove the change of default CR if possible. Checked and it turned out, that we still have issues with the AR. I will create another issue for the AR. |
fixed review findings
Ok, is it ready to go? |
yepp, it should be good to go |
Refactored crosscut functionality.