Android ArrayAdopter has way to override getFilter() method which means someone has to implement all filter methods.
Why is this designed so badly.. I would have expected it to be standard filter listener, which can supplied to ArrayAdopter, which has one method
boolean doFilterCheck(Object listItem, String searchString)
This way, the user would have take listitem details and do all it requires to say if this is needs to be shown or not as per his custom logic.
Lack of all these, we now need to keep track of all the list items, iterate our self, clean up the list and add only relevant ones.. What a for sure buggy overhead..(what happens if one removes list items left and right..)
I can't expect android designers to be so cruel in design of ArrayAdopter. Hence wish someone out there tell me what is that I am missing to understand on the current api design of ArrayAdopter w.r.t to Filter
0 comments:
Post a Comment