SlickEdit Community
SlickEdit Product Discussion => SlickEdit® => Topic started by: MiloDC on July 26, 2006, 10:31:42 AM
-
After purchasing v11 and immediately updating to 11.0.1, identification of errors by the Java Live Errors feature is persistent.
i.e. Once I correct an error, neither the white X in the little red circle nor its corresponding red underlining vanish. They stick around for the remainder of the SlickEdit session.
Is this some new 11.0 functionality of which I'm unaware?
-- Milo
-
After purchasing v11 and immediately updating to 11.0.1, identification of errors by the Java Live Errors feature is persistent.
i.e. Once I correct an error, neither the white X in the little red circle nor its corresponding red underlining vanish. They stick around for the remainder of the SlickEdit session.
Is this some new 11.0 functionality of which I'm unaware?
-- Milo
Did you find a solution to this problem?
Thanks
-
The Java Live Errors feature was disabled in 11.0. In it's stead, we have opted to use a somewhat less dynamic technique for displaying build errors, which simply scans your compiler output for errors and displays the error markers in your source. Naturally, in this case, the error markers will not just go away as you edit, but they should go away the next time you build. Also, in 11.0, you can configure SlickEdit to start a build every time you save a file in your current project, which will result in the error markers being updated.
You can re-enable Java Live Errors by going to Build > Java Options, and turning on Live Errors, however, due to numerous limitations in the Jikes compiler, there is no support for Java 1.5 language features. We are continuing to investigate finding a suitable alternative to using Jikes.