Ability to clear problem markers created by Crystal

roterdam / crystalsaf

Automatically exported from code.google.com/p/crystalsaf

0 stars 0 forks source link

Ability to clear problem markers created by Crystal #3

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago

This is low priority, but it would be nice to be able to clear problem 
markers created by Crystal before giving a demo.  That way there will be no 
problems shown until after the analysis has been run.

Original issue reported on code.google.com by aldrich....@gmail.com on 10 Sep 2008 at 3:14

GoogleCodeExporter commented 9 years ago

Classified this issue.

Original comment by aldrich....@gmail.com on 10 Sep 2008 at 4:14

Added labels: Component-UI, Priority-Low, Type-Enhancement
Removed labels: Priority-Medium, Type-Defect

GoogleCodeExporter commented 9 years ago

Your wish is our... something.

This issue has been fixed in Revision 81. There is now a menu item in the 
Crystal 
menu that clears every Crystal warning in the entire workspace, but no other 
warnings.

Original comment by nels.bec...@gmail.com on 10 Sep 2008 at 9:33

Changed state: Fixed

GoogleCodeExporter commented 9 years ago

After updating Crystal, re-running Crystal may not remove existing problem 
markers,
and the new menu item won't remove those, either.  Markers produced by Crystal 
runs
after the update will be removed fine.

It turns out you can manually delete problem markers from Eclipse's problems 
view,
which is probably the easiest way of getting rid of old markers.  You can also 
change
the first parameter to the call to "deleteMarkers" in Crystal's 
ClearWarningHandler
class to "IMarker.Problem", run Crystal, and use the new menu item to remove 
legacy
markers.

Original comment by kevin.bi...@gmail.com on 11 Sep 2008 at 3:27