The 0.13 version does not contain a lot of new exciting features, the main focus of this version was to fix a couple of not so crucial bugs and to make sure that we will not have possible memory leaks when adding/removing InputAssist component to the DisplayList.

The only "new" feature is that InputAssist now supports dataProvider typed as ArrayList.

    Here is the full changelist for this release:

[!] Fixed issue with resetting visible "prompt" value when changing dataProvider
[!] Fixed issue by keyboard navigation by the help of Keyboard.UP and Keyboard.DOWN buttons
within option list if option list was closed and reopened.
[!] Items that had "-" or "+" symbols in its labels were not properly filtered
[!] Creating complete copy of passed ArrayCollection into dataProvider to avoid filtering of the original data source
[!] Fixed RTE when using InputAssist control within Adobe AIR app in "onFlexWindowActivate" event listener
[!] Started to use weak references when adding event listeners to avoid possible memory leaks
[!] "dataProvider" property now accepts data list typed as ArrayList.

As always, the most recent source code of the component and compiled SWC library file is available at GitHub

As always the latest source code and SWC file can be downloaded from GitHub:http://github.com/JabbyPanda/InputAssist

Short description of new features:

"processing" property
   Quite often the long data list is being loaded into InputAssist control asynchronously from remote destinations. Now InputAssist is able to display "hourGlass" icon during the data loading process by controlling "processing" property.

"errorMessage" property
    If InputAssist's dataProvider is currently empty, then there is nothing to be chosen from. Displaying "errorMessage" text and disabling the control gives the user the right UI feedback about the component state.

"prompt" property
   If no value is not selected yet via InputAssist control, the control can display text specified by the "prompt" value to explain what action is expected to be taken from the user side.

   Alternative usage of "prompt" property that I can think of - is to display the suppossedly selected current data object label which is not present in the InputAssist's dataProvider list == e.g. this selected data object is not valid and should be altered by the further user action.

And yes, sorry about long time delay to retrieve city list in the demo below, it is not a component fault, but long service time response from api.business.gov

Changelog for 0.12 release:
[+] Added property "prompt"
[+] Added property "errorMessage"
[+] Added property "processing"

[!] Fixed issue with dispatching InputAssistEvent.CHANGE event for nullable selectedItem
[!] Fixed issue with auto-completion by hitting ENTER key

The source code will be permanently available at GitHub (yes, new kid in the block instead of Google Code or SourceForge).

http://github.com/JabbyPanda/InputAssist/

Demo:

Changelog for 0.1 release:

[+] Added style "highlightBackgroundColor" to InputAssist
[+] Added Ant build script
[+] Packaged as SWC library

[*] Changed classes namespace to match industry standard
[*] Changed the algorithm for the highlighting of matched text segments, thankfully to
Maxim Kachurovsky "Slov v sapogah" for an idea

[!] Fixed the appearance of popup list when "forceAuto" option is on and
system focus is moved back and forth between 2 different instances of FocusManager class.