We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the node creation strategy needs to be created before we add elements to the drawable.
This is counter-intuitive because the rest of the Telescope API does not need an order.
We should be able to invert the order of the messages.
The text was updated successfully, but these errors were encountered:
visu nodeCreationStrategy compositeProperty: #types; compositeChildrenLayout: (TLLinearLayout gap: 20 ratio: 16 / 9). packages := visu addNodesFromEntities: (model allModelNamespaces sort: [ :p1 :p2 | p1 mooseName <= p2 mooseName ]).
Should produce the same as
packages := visu addNodesFromEntities: (model allModelNamespaces sort: [ :p1 :p2 | p1 mooseName <= p2 mooseName ]). visu nodeCreationStrategy compositeProperty: #types; compositeChildrenLayout: (TLLinearLayout gap: 20 ratio: 16 / 9).
Sorry, something went wrong.
No branches or pull requests
Currently, the node creation strategy needs to be created before we add elements to the drawable.
This is counter-intuitive because the rest of the Telescope API does not need an order.
We should be able to invert the order of the messages.
The text was updated successfully, but these errors were encountered: