I'll worked w/similar components. One thing that helps is to have each
keypress schedule an autocomplete to take place in the future (e.g. in
100ms), and each keypress resets/restarts the timer. That way, if the user
knows where they are going, you are not unnecessarily doing processing.
Also, d
Hi,
> When I used it with the component, it works but it has become slow probably
> because of
> filtering of the xmllistcollection on each key press.
It may depends on your filter function. XML operations are generally slower
than operations on other types. You should see some speed improvemen
I believe the filterFunction goes over each item separately and treats each
item as an Object. So if you had 900k records, it should be a consistent
(slow) speed for each key-press. The more logic is in your filterFunction
the more compounded the effects you should see in the speed (slower with
m
