You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Error and warning icon decorations in AADL Navigator are not updated #1824
changed the title [-]Error markers in AADL Navigator are not updated[/-][+]Error and warning icon decorations in AADL Navigator are not updated[/+]on Jun 3, 2019
Made AadlElementContentProvider an IResourceChangeListener. It forces a refresh of the associated viewer when a change event comes through.
I tried to make the refresh "smart" and only update the viewer when .aadl files are changed, but that didn't work because all the events that came thorugh just indicated that the workspace root had changed. So it didn't make sense to do any fancy checking.
Activity
[-]Error markers in AADL Navigator are not updated[/-][+]Error and warning icon decorations in AADL Navigator are not updated[/+]AaronGreenhouse commentedon Jun 19, 2019
Need to figure out how to trigger a refresh in the common navigator.
I see an odd thing in the
plugin.xmlfororg.osate.ui. Note theviewerRefresherin the definition of theAadlNavigator:The problem is there is no mention of this any where else. The name doesn't seem to be bound to anything.
AaronGreenhouse commentedon Jun 19, 2019
The Eclipse forum here may be useful, but the original question seems to be imcompletely answered: https://www.eclipse.org/forums/index.php/t/154948/
AaronGreenhouse commentedon Jun 19, 2019
These seems more helpful: https://subscription.packtpub.com/book/application_development/9781783287796/1/ch01lvl1sec09/common-navigator
AaronGreenhouse commentedon Jun 20, 2019
Made
AadlElementContentProvideranIResourceChangeListener. It forces a refresh of the associated viewer when a change event comes through.I tried to make the refresh "smart" and only update the viewer when .aadl files are changed, but that didn't work because all the events that came thorugh just indicated that the workspace root had changed. So it didn't make sense to do any fancy checking.