Fix persistent "empty name" error.

We were never clearing the error state when typing in a field that
needed to be non-empty.

Bug: 5422268
Change-Id: Iabe8c6f6c348b4210695c3eeff98e79e60f83d08
This commit is contained in:
Ben Komalo 2011-10-07 18:03:16 -07:00
parent dbd2aeda76
commit c35c4b14c9

View File

@ -74,13 +74,16 @@ public class AccountSetupNames extends AccountSetupActivity implements OnClickLi
mNextButton.setOnClickListener(this);
TextWatcher validationTextWatcher = new TextWatcher() {
@Override
public void afterTextChanged(Editable s) {
validateFields();
}
@Override
public void beforeTextChanged(CharSequence s, int start, int count, int after) {
}
@Override
public void onTextChanged(CharSequence s, int start, int before, int count) {
}
};
@ -162,16 +165,18 @@ public class AccountSetupNames extends AccountSetupActivity implements OnClickLi
* Check input fields for legal values and enable/disable next button
*/
private void validateFields() {
boolean newEnabled = true;
boolean enableNextButton = true;
// Validation is based only on the "user name" field, not shown for EAS accounts
if (!mEasAccount) {
String userName = mName.getText().toString().trim();
newEnabled = !TextUtils.isEmpty(userName);
if (!newEnabled) {
if (TextUtils.isEmpty(userName)) {
enableNextButton = false;
mName.setError(getString(R.string.account_setup_names_user_name_empty_error));
} else {
mName.setError(null);
}
}
mNextButton.setEnabled(newEnabled);
mNextButton.setEnabled(enableNextButton);
}
/**