-
Notifications
You must be signed in to change notification settings - Fork 274
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
Add more detailed address error message #533
Conversation
Concept ACK |
1c119d9
to
d90ca37
Compare
Force-pushed with following changes: . Manually changed
|
Concept ACK |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think, at the GUI level, we need to present the user with such detail. A translatable message that conveys the entered address is not correct is enough. If presenting the internal error message is useful for developing purposes, perhaps detailed error messages can be enabled through GUI settings added under a developer mode tab.
We can't display a translated error message with this approach and per our translation policy
gui/doc/translation_strings_policy.md
Lines 26 to 27 in e3ce019
Do not translate technical or extremely rare errors. | |
Anything else that appears to the user in the GUI is to be translated. This includes labels, menu items, button texts, tooltips and window titles. |
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ReviewsSee the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
These are technical errors so policy is still followed. |
I built and ran this, I think it's an interesting experiment, (this is not nak, but yet far from concept ack as well) |
<item row="2" column="1"> | ||
<widget class="QLabel" name="errorMessage"> | ||
<property name="styleSheet"> | ||
<string notr="true">color:red;</string> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is hardcoded red color visually compatible with dark themes/appearance? Maybe add some relevant screenshots?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a screenshot posted by @jonatack here:
#534 (review)
But this style is already used in sendcoinsdialog.ui
and sendcoinsdialog.cpp
for invalid custom change addresses and insufficient funds , so it seems to be a well tested configuration.
🐙 This pull request conflicts with the target branch and needs rebase. Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft". |
I agree with others that it looks a bit weird when there is no error. Perhaps move it to the tooltip? |
There hasn't been much activity lately and the patch still needs rebase. What is the status here?
|
There hasn't been much activity lately and the patch still needs rebase. What is the status here?
|
1 similar comment
There hasn't been much activity lately and the patch still needs rebase. What is the status here?
|
Closing due to lack of interest. |
fe7c81e qt: change QLineEdit error background (w0xlt) Pull request description: This PR proposes a small change in QLineEdit when there is an error in the input. master | --- | ![image](https://user-images.githubusercontent.com/94266259/154762427-b816267e-ec70-4a8f-a7fb-1317ebacf1a4.png) PR | --- | ![image](https://user-images.githubusercontent.com/94266259/154761933-15eb3d81-ca81-4498-b8ec-cf1139ae2f8a.png) | This also shows good results when combined with other open PRs. #537 | --- | ![image](https://user-images.githubusercontent.com/94266259/154763411-6266a283-2d8a-4365-b3f2-a5cb545e773e.png) #533 | --- | ![image](https://user-images.githubusercontent.com/94266259/154765638-f38b13d6-a4f8-4b46-a470-f882668239f3.png) | ACKs for top commit: GBKS: ACK fe7c81e jarolrod: ACK fe7c81e shaavan: ACK fe7c81e Tree-SHA512: eccc53f42d11291944ccb96efdbe460cb10af857f1d4fa9b5348ddcb0796c82faf1cdad9040aae7a25c5d8f4007d6284eba868d7af14acf56280f6acae170b91
When reviewing bitcoin/bitcoin#24106, I noticed that GUI does not provide a clear reason for invalid addresses. Basically it just changes the
QLineEdit
to red color.This PR adds a more detailed error message. The motivations are:
. Provide more information about the error and improve the user experience.
. When a more subtle error occurs, as the one detailed in bitcoin/bitcoin#24106, the user can understand what is happening.
To test this PR, enter invalid addresses in the
Pay To
field on theSend
tab and also in the address manager (icon next toPay To
).