Under what circumstances should I use afterTextChanged instead of onTextChanged and vice versa?
Under what circumstances should I use afterTextChanged instead of onTextChanged and vice versa?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Under what circumstances should I use afterTextChanged instead of onTextChanged and vice versa?
These events are called in the following order:
beforeTextChanged(CharSequence s, int start, int count, int after).
This means that the characters are about to be replaced with some new text. The text is uneditable.
Use: when you need to take a look at the old text which is about to change.
onTextChanged(CharSequence s, int start, int before, int count).
Changes have been made, some characters have just been replaced. The text is uneditable.
Use: when you need to see which characters in the text are new.
afterTextChanged(Editable s).
The same as above, except now the text is editable.
Use: when you need to see and possibly edit the new text.
If I’m just listening for changes in
EditText, I won’t need to use the first two methods at all. I will just receive new values in the third method and correct new text if needed. However, if I had to track down exact changes which happen to the values, I would use the first two methods. If I also had a need to edit the text after listening to the changes, I would do that in the third method.