Java Client: Don't disable buttons when password is blank
This would be better fixed by having native return an empty string instead of null, but I don't know what sort of side effects that would have elsewhere
This commit is contained in:
parent
63c211922f
commit
900ce4baa3
@ -950,11 +950,11 @@ public class UserContentPanel extends JPanel implements MasterPassword.Listener,
|
||||
resultField.setText( EACH_CHARACTER.matcher( result ).replaceAll( "•" ) );
|
||||
else
|
||||
resultField.setText( result );
|
||||
settingsButton.setEnabled( result != null );
|
||||
questionsButton.setEnabled( result != null );
|
||||
editButton.setEnabled( result != null );
|
||||
keyButton.setEnabled( result != null );
|
||||
deleteButton.setEnabled( result != null );
|
||||
settingsButton.setEnabled( site != null );
|
||||
questionsButton.setEnabled( site != null );
|
||||
editButton.setEnabled( site != null );
|
||||
keyButton.setEnabled( site != null );
|
||||
deleteButton.setEnabled( site != null );
|
||||
} );
|
||||
}
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user