[JDT_UI]Custom IMarkers visible in CompilationUnitEditor [message #64206] |
Sat, 21 June 2003 23:29  |
Eclipse User |
|
|
|
Given:
IMarker marker =
method.getCompilationUnit().
getCorrespondingResource().
createMarker(IMarker.PROBLEM);
marker.setAttribute(IMarker.SEVERITY, IMarker.SEVERITY_ERROR);
marker.setAttribute(IMarker.MESSAGE, message);
marker.setAttribute(IMarker.CHAR_START, start);
marker.setAttribute(IMarker.CHAR_END, length);
The markers I create show up in the Tasks view but not in the
compilation unit editor. I want them to show up as squiggly underlines
in the compilation unit editor as well, but have not discovered how to
make this happen. All the code that does this inside JDT appears to be
in internal packages; is there an external API that will let me do this?
Thanks in advance,
Dave
|
|
|
|
Re: [JDT_UI]Custom IMarkers visible in CompilationUnitEditor [message #66544 is a reply to message #65772] |
Tue, 24 June 2003 23:42  |
Eclipse User |
|
|
|
Daniel Megert wrote:
> David J. Orme wrote:
>
>> Given:
>>
>> IMarker marker =
>> method.getCompilationUnit().
>> getCorrespondingResource().
>> createMarker(IMarker.PROBLEM);
>> marker.setAttribute(IMarker.SEVERITY, IMarker.SEVERITY_ERROR);
>> marker.setAttribute(IMarker.MESSAGE, message);
>> marker.setAttribute(IMarker.CHAR_START, start);
>> marker.setAttribute(IMarker.CHAR_END, length);
>>
>>
>> The markers I create show up in the Tasks view but not in the
>> compilation unit editor. I want them to show up as squiggly
>> underlines in the compilation unit editor as well, but have not
>> discovered how to make this happen. All the code that does this
>> inside JDT appears to be in internal packages; is there an external
>> API that will let me do this?
>
>
>
> See org.eclipse.ui.texteditor.MarkerUtilities
>
> For more info search (http://www.eclipse.org/search/search.cgi) the news
> archive for similar questions. This has been answered many times.
Ooooops. You're right; I should have STFN first.
Thanks,
Dave
|
|
|
Powered by
FUDForum. Page generated in 0.04600 seconds