-
Notifications
You must be signed in to change notification settings - Fork 14
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
Refresh issue in Model Explorer with custom Content Provider #101
Comments
Bug: #101 Signed-off-by: Pierre-Charles David <[email protected]>
Hi Yann! 👋 It's difficult to test if it requires a custom content provider, but can you verify if the PR above fixes the issue for you? |
Hello @pcdavid The refresh is invoked with your changes. We still need to add some custom refresh because Sirius refreshes only impacted elements and we want to use a custom CNF Content Provider to filter out some intermediary elements. For example, using ecore, the Model Explorer shows:
We want to hide EClass elements (only in Model Explorer):
The refresh limits the scope to Lines 986 to 994 in a0a0e0a
We can not rely on this mechanism because if an I think we should manage our custom refresh in our custom providers like EMF does. What are your thoughts? |
Bug: #101 Signed-off-by: Pierre-Charles David <[email protected]>
The variable
result
inorg.eclipse.sirius.ui.tools.internal.views.common.navigator.SiriusCommonContentProvider.RefreshViewerTriggerScope.isSemanticChange
is never set (see line 1071):sirius-desktop/plugins/org.eclipse.sirius.ui/src/org/eclipse/sirius/ui/tools/internal/views/common/navigator/SiriusCommonContentProvider.java
Lines 1068 to 1074 in a0a0e0a
A consequence is the model explorer is not refreshed by
RefreshViewerTrigger
on semantic change.The Model Explorer still works with raw Sirius because contributions to the Model Explorer in Sirius use the
AdapterFactoryContentProvider
which is able to refresh the viewer on semantic changes.If another plugin (outside of Sirius) contributes new content providers to the Model Explorer without using
AdapterFactoryContentProvider
then it has to manage the refresh on semantic changes (by copying the whole refresh process which can be error prone).The text was updated successfully, but these errors were encountered: