Community
Participate
Working Groups
When the model explorer is invisible (e.g. the project navigator is shown), it does not capture resource changes. This would not be a problem if it refreshes once visible again. This is however not the case. Reproduce: 1. open a model. Open model explorer, then hide it (e.g. change tab). 2. Now make a change in the model, e.g. rename an element via a diagram. 3. Make the model explorer visible again. 4. It still contains the old name
The refresh operation in ModelExplorerView.java checks the isVisible attribute, i.e. the refresh is not execute if not visible. A simple solution is to skip this check (done in current fix), i.e. to refresh even if not visible. A potential alternative is to set an "needsRefresh" check and executes the refresh once the explorer is visible again. [good, if a multiple refresh operations are executed while invisible. But the graphic operations are not executed anyway while invisible => minor optimization?]
It seems that this bug is not valid anymore