Community
Participate
Working Groups
All IDEs update the Syntax errors when code changes. Unfortuantely in Eclipse, one neeeds to save the file to get this pane refreshed. This is very annoying. Can this behaviour be changed? so that When code is changed resulting in an error , the problems view gets refreshed?
The editor merges problems issued from last official compile (when building) and those issued when reconciling user input. This is rendered in editor only. You may discard editor changes for instance, and these extra problems would simply disappear then. If real markers were created and rendered in problem view, these would broadcast changes to clients, where these have no incidence on clients until: 1- editor contents is saved 2- classfiles are regenerated. So editor problems are rather a preview of what you will see when the next build will occur. The reason why save seems to refresh the problem view, is that you are running on autobuild, where a build automatically takes place each time you save a file or modify any file.
The Problems view could also show the annotations via text file buffer's annotation model.
I don't think it makes sense to add specific code to the problems view to detect annotations in the text editor, as this would only work for the problems view and not other views that indicate problem state such as the annotations in the package explorer. I would either expect it to behave like this everywhere or nowhere. This should be part of some more general facility that allows clients to examine and listen to changes in unsaved IMarkers (aka annotations) in the same way they can listen to IMarker changes in the workspace.... or we should flag this as invalid. If we opt for the former, then the problems view would behave largely like it does now, but it would simply search a different tree for its markers.
Moving to core, since that's where the support would need to start.
Sorry, the problems view will only update when the file is saved. It is too expensive to be constantly update all these annotations as you type.
*** Bug 470927 has been marked as a duplicate of this bug. ***
