Small change by altering the text values for the request payment button and it's tab description to the ones suggested in #14482.
Closes #14482
utACK 59a9bd6d5895f0a2d96b505b73ed0ef1060c919c. Though we should probably discuss how we could remove the address book and eventually increase the usability of per-transaction comments and labels.
utACK https://github.com/bitcoin/bitcoin/pull/14484/commits/59a9bd6d5895f0a2d96b505b73ed0ef1060c919c @jonasschnelli agreed, this is a good first step for usability though
I can surely help with improving per-transaction comments and labels if you point me in the right direction.
107 | @@ -108,7 +108,7 @@ 108 | </size> 109 | </property> 110 | <property name="text"> 111 | - <string>&Request payment</string> 112 | + <string>&Receive payment</string>
This doesn't seem literally correct. Receiving only happens when the sender sends. :/
Should this text even change than. As far as I understand it's function it makes sense.
maybe call it something like "Create new receiving address" instead? (I guess "request payment" was also not literally correct, since it doesn't send a payment request anywhere AFAICT)
Will do.
106 | @@ -107,7 +107,7 @@ AddressBookPage::AddressBookPage(const PlatformStyle *platformStyle, Mode _mode, 107 | ui->newAddress->setVisible(true); 108 | break; 109 | case ReceivingTab: 110 | - ui->labelExplanation->setText(tr("These are your Bitcoin addresses for receiving payments. It is recommended to use a new receiving address for each transaction.")); 111 | + ui->labelExplanation->setText(tr("These are your Bitcoin addresses for receiving payments. Use the request payment button in the receive tab to create new addresses."));
If the button is getting renamed, it doesn't make sense to refer to the old name here.
Agreed
106 | @@ -107,7 +107,7 @@ AddressBookPage::AddressBookPage(const PlatformStyle *platformStyle, Mode _mode, 107 | ui->newAddress->setVisible(true); 108 | break; 109 | case ReceivingTab: 110 | - ui->labelExplanation->setText(tr("These are your Bitcoin addresses for receiving payments. Use the request payment button in the receive tab to create new addresses.")); 111 | + ui->labelExplanation->setText(tr("These are your Bitcoin addresses for receiving payments. Use the 'Create new receiving address' button in the receive tab to create new addresses."));
Nit: Prefer to have the button label here as a %1 token, so translations don't need to change when/if we rename the button again. (OTOH, the button itself needs &, so maybe not worth the trouble...)
107 | @@ -108,7 +108,7 @@ 108 | </size> 109 | </property> 110 | <property name="text"> 111 | - <string>&Receive payment</string> 112 | + <string>&Create new receiving address</string>
Please keep r as the accelerator key.
I think we shouldn't rush as this doesn't look consistent:
<img width="876" alt="screenshot 2018-10-15 at 13 54 23" src="https://user-images.githubusercontent.com/3534524/46952283-511d4a00-d082-11e8-81bb-c7e55c3b947c.png">
I agree with @jonasschnelli, first discuss, mock etc, and them implement?
I think we shouldn't rush as this doesn't look consistent:
<img alt="screenshot 2018-10-15 at 13 54 23" width="876" src="https://user-images.githubusercontent.com/3534524/46952283-511d4a00-d082-11e8-81bb-c7e55c3b947c.png">
I agree with @jonasschnelli, first discuss, mock etc, and them implement?
Ok so what is the scope of these changes. Should this be done in the course of this issue?
This seems to have bled out a bit.
I think this is a general improvement. We can do further extensions/cleanup later. Lets merge this. utACK c46a603d7a149efa1e7af596e5437156d26742ac @HatboyWonder: can you squash the second commits since its basically overwriting your first commit.
@jonasschnelli squashed/rebased in #15829.