Skip to content

Conversation

@dvojtise
Copy link
Contributor

With some models, Sirius session returns a new resourceSet instead of using the one we provided in the DefaultModelLoader. (ex: Capella)

This ends up with 2 different resources, one for the execution and one for the animation.

This PR makes sure to get a single resource (the one create by the sirius session)

However, I'm not sure this can also handle melange query (ie. "downcasting" model) so I added a warning if this situation occurs while using melange queries.

in some situations, the resourceSet we create is not used by Sirius for
its session.
In that case, we need to load the model from this resourceSet instead o
the one we created.

Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
Signed-off-by: Didier Vojtisek <didier.vojtisek@inria.fr>
@dvojtise dvojtise added the bug label Dec 16, 2019
@dvojtise dvojtise merged commit 3464323 into master Dec 16, 2019
@dvojtise dvojtise changed the title Handle Sirius forced resource set Handle Sirius forced resourceSet Dec 16, 2019
@dvojtise dvojtise deleted the handle_sirius_forced_resourceSet branch December 17, 2019 15:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants