What are you trying to do? Can you elaborate a little bit? I guess you want an Autocomplete textview that is capable of having multiple values, something like an email to field. If this is the case, you have a simpler solution. Just change the way, AutoCompleteTextView behaves.
Here is an article that might help you. http://tech-droid.blogspot.com/2010/04/custom-autocomplete-for-android.html Thanks and Regards, Kumar Bibek On Apr 9, 6:35 pm, Al <[email protected]> wrote: > I have a (Multi)AutoCompleteTextView which uses an item click > listener. I received a crash report which shows a NPE in > onItemClick(). In onItemClick, I use the selected view (param #2 of > the listener) to do manipulation to the text, but looking at the > source code for AutoCompleteTextView and it has the following block: > > // Note that we don't have a View here, so we will need to > // supply null. Hopefully no existing apps crash... > mItemClickListener.onItemClick(list, null, > completion.getPosition(), > completion.getId()); > > Shouldn't the onItemClick listener always receive a non-null value for > view? The docs (http://min.ie/3mr) say: > view - The view within the AdapterView that was clicked (this will be > a view provided by the adapter) > > Am I correct in assuming this is a bug? The stack trace can be seen > here:http://paste2.org/p/765292 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en To unsubscribe, reply using "remove me" as the subject.
