Make @OnTextChanged more useful when using multiple Views

@OnTextChanged can be applied to methods with different signatures that mirror TextWatcher’s before/after/onTextChanged() methods. But none of those possible signatures include the View that was annotated. When specifying multiple Views, it doesn’t seem to be possible to associate that callback to the View whose text changed. For example:

@OnTextChanged({R.id.edittext_foo, R.id.edittext_bar})
protected void handleTextChange(Editable editable) {
    // I have the Editable that changed but which View's Editable is it???
}

For comparison, the signatures accepted for @OnCheckChanged and @OnClick include the View. Are there technical reasons why it would be impractical to include the Editable’s View as a parameter?

[arunseshagiri]

below code can be used to get the current view,

//Inside a activity View view = getCurrentFocus();

with this view object you can get the id view.getId(); and use the same for comparison.

Hope this helped.

[JakeWharton]

My biggest objection is that this would require specialization of a mechanism which is currently general. The reason those other listeners allow receiving the view is because their associated callback does as well.

On Tue, Jul 12, 2016 at 6:31 PM Brandon Rich [e-mail] wrote:

@OnTextChanged can be applied to methods with different signatures that mirror TextWatcher’s before/after/onTextChanged() methods. But none of those possible signatures include the View that was annotated. When specifying multiple Views, it doesn’t seem to be possible to associate that callback to the View whose text changed. For example:

@OnTextChanged({R.id.edittext_foo, R.id.edittext_bar}) protected void handleTextChange(Editable editable) { // I have the Editable that changed but which View’s Editable is it??? }

Not being able to associate the change to the View that changed prevents me from being able to use Butterknife for these listeners. In contrast, the signatures accepted for @OnCheckChanged and @OnClick include the View.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/JakeWharton/butterknife/issues/672, or mute the thread https://github.com/notifications/unsubscribe/AAEEEWjOZUCsHr6dVQnZu3-kyN-Q6w7dks5qVBXKgaJpZM4JK5Op .