Community
Participate
Working Groups
It would be fine if the right-click menu which appears when you click on the vertical or overview ruler were to have a submenu for temporarily turning on/off the display of certain annotation types (e.g. Errors, Warnings, Tasks, etc.). This can be useful in various situations -- one of them could be when first developing a source file, where things are not yet complete, and you don't want a bunch of errors to be reported yet.
I'm not sure if you saw that: using 3.4 or newer you have two choices: 1. hover over the text where the annotation appears and click on the 'Configure' button. This takes you directly to the 'Annotations' preference page. If you opened the context menu on an annotation it will directly pre-select that annotation. 2. in the Overview ruler (right side) open context menu > Preferences... which takes you directly to the 'Annotations' preference page. If you opened the context menu on an annotation it will directly pre-select that annotation. I think that's fast enough. In an install with many plug-ins there will be many annotation types and hence a sub-menu becomes unhandy (at least for enabling new annotation types).
Ok, I can accept that using the preferences panel is 'sufficiently fast', but it doesn't address the other (perhaps more important) part of the feature request: There should be *default* annotation settings, and *temporary* annotation settings. The temporary just modifies what you see for the moment, and then you can revert these temporary settings, or when you next restart eclipse, they will be reverted. Also, it seems that the annotation settings are application-wide. Making them temporary and per-editor-window (or per-file) would allow the possibility of showing some annotations on a certain file or kind of file, and another set of annotations for other kinds of files.
Sorry, there are no plans to do something like that.
Keeping open, in case someone else is interested in doing this.
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
