-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IP Address input value control - move validation and persistence out from onTextChanged into onEditingFinished but needs UI change (maybe adding a new "done" button) #438
Comments
Here is a reference for this pattern, from editing your name in iOS account settings. There are probs some details we should define, like:
Just some thoughts. What are yours? |
I agree, makes sense, that could work.
I was thinking on that yesterday night and I was going to create a separate issue today, because other settings could need this feature as well. (edit: #419)
I need to check, perhaps we could ask the user if he want to restart and do it for him. At the moment in Qt requires manual restart from the user.
Yes, losing focus makes sense to validate but to persist the value only with "Done". Also in the proxy settings we have the default proxy and the tor one, this "Done" is for both? Or independent: the user needs to finish with "done" the default before modifying the tor? And then as soon the default's "done" disappears another would come back if the user starts editing the tor input? |
Brings the mock-ups in line with the recent work in issues and PRs. For max upload limits: #8 For the proxy screen: #43 bitcoin-core/gui-qml#438
Brings the mock-ups in line with the recent work in issues and PRs. For max upload limits: #8 For the proxy screen: #43 bitcoin-core/gui-qml#438
Now, every time a user types into the ip address input value, the value is validated and persisted (if #433 gets merged), this is because of the nature of the app design, there's no where to "accept" the changes or land after editing a value. Originally the validation was triggered in the editing finished but it seemed more correct to move it into the text change due to the above reason. But when we added the persistence logic (#433), didn't feel right anymore, so @GBKS suggested to add a "done" button when we revert back to the correct event again:
The text was updated successfully, but these errors were encountered: