Last night, RSyntaxTextArea 1.4.2 was released on SourceForge! That includes new releases of RSyntaxTextArea as well as AutoComplete and SpellChecker. This release was mostly about bug fixes and improvements in code completion behavior. Here’s a quick list of all of the changes in this release.
- Groovy syntax highlighting updates (GDK Object methods, Java 5/6 java.lang classes, URL’s in comments)
- A fix to prevent security exception when setting AA hint in an applet (thanks to Frederic in the forums)
- Fixing positioning of FocusableTips and code completion windows on multi-monitor setups (thanks to grzlbrmft in the forums for the bug report and testing). I’m personally jealous of everybody out there with a dual monitor setup, who got to experience this bug. 🙂
- AutoComplete’s description window now updates itself in response to a selection change after a small delay (120ms) instead of immediately, to help performance for language supports with slower descriptions (e.g. file IO). This mimics Eclipse’s behavior.
- Added ActionScript syntax highlighting. Perhaps now I have no excuse to play with this language.
- Improved performance of auto-completion list cell renderer for huge completion lists. Helps with languages with huge amounts of functions, such as PHP.
- When using SearchEngine, if the next match isn’t currently visible, center the found/replaced text after the search operation. This is a seemingly small change but is a nice usability improvement, and is seen in better editors like Eclipse. For example, if your cursor is here:
And you used SearchEngine#find() in RSTA 1.4.1 to find the next instance of “clip”, the next instance would be selected and brought into the visible area like so:
Note that the next instance is selected, but is barely scrolled into the view. Starting with 1.4.2, the next match is scrolled to the center of the text area, vertically:
If the next instance of the text you’re searching for is already visible, the editor is not scrolled, the text is merely selected. If the next match is not currently visible, however, that’s when it will be scrolled to the center of the view.
- Fix for SourceForge bug 2998448: regex “replace all” is always case-sensitive.
- SearchEngine’s concept of “whole word” is more accurate now (allows for punctuation, such as ‘,’, at the end of words, for example). Previously, a “whole word” had to be completely surrounded by whitespace.
- Added start of JUnit tests for SearchEngine.java.
- SearchEngine bug fixes for replaceAll() with regex and match case/whole word enabled.
- Fixed auto-complete bug with overloaded functions.
- Fixed auto-complete bug – capitalization should be corrected when completing a parameterized completion.
- Improved properties file syntax highlighting: ‘:’ can divide name/value pairs.
- Added “our” keyword to Perl syntax highlighting.
Grab it on the SourceForge page today!