I’m happy to announce that we just released version 1.2 of our client-side, check-as-you-type, spell checking library for ActionScript 3 projects in Flash, Flex, or AIR. This version includes some significant updates including:
- rewritten spelling suggestions algorithm, which is faster and returns better results
- better support for AIR, and addition of an AIRMenuHelper class to reinsert editing options
- enhanced multi-line highlighting
- improved support for languages other than English
- RegExpHighlighter source code, which highlights matches for a regular expression in a text field (as seen at regexr.com)
- various minor bug fixes and enhancements
SPL 1.2 is a free upgrade for current users. If you own a license to SPL, and have not received the update package, please contact us through the support form on our product site.
You can find more information on the Spelling Plus Library, and see demos of it in action at the SPL product page.
We are using SPL 1.2. I’ve also integrated the SpellingWindow in the Flex demos into my application with a few modifications.
I am using your library to spell check the text inside several TextInput controls in a Form. The library is working great. My problem though, is that I am using tags to bind the text back to it’s XML data source. When I change the text in the TextInput programmatically after a user chooses to Change a misspelled word, the original XML data source is not updated. It seems to only work when there is user interaction. The TextInput’s Change event is also being fired after the text is changed and still the Binding wont fire. I would think this is a common issue others using your library have ran into and am looking for the best solution to resolve this. I want to avoid have to Bind manually if it is possible. Any suggestions?
Grant, SPLTagFlex takes up space in the application. I had extra padding and moved my two SPLTagFlex instances and the padding was gone. I put them back with includeInLayout=”false” and the padding is gone, as expected.
Just an FYI and I didn’t see a support page for it.
Thanks for the heads up John. We’re working on the next release now, and this will be an easy one to fix.