You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For Qtum-Qt v0.18.3, v0.18.2, maybe earlier, on the Send Coins page, after entering the amount to send in the Amount textbox, with the cursor in that textbox, pressing the "Enter" key will change that amount to the "use available balance" amount (Windows) or 0.0 (Linux). If the amount is entered and then clicked away from the Amount textbox, the amount will be shown correctly. Perhaps the focus must be set on the Amount textbox. Repeatable.
This works correctly for the Amount textbox on Send QRC20 tokens page. Pressing the “Enter” key after entering an amount on the Send to Contract Page Optional Amount textbox will highlight the amount but does not validate that amount.
Also, for the Amount textboxes, the increment/decrement control changes the amount of QTUM by 0.001 per click and for QRC20 tokens by 0.1 per click. Would 1.0 per click be more useful?
The text was updated successfully, but these errors were encountered:
For Qtum-Qt v0.18.3, v0.18.2, maybe earlier, on the Send Coins page, after entering the amount to send in the Amount textbox, with the cursor in that textbox, pressing the "Enter" key will change that amount to the "use available balance" amount (Windows) or 0.0 (Linux). If the amount is entered and then clicked away from the Amount textbox, the amount will be shown correctly. Perhaps the focus must be set on the Amount textbox. Repeatable.
This works correctly for the Amount textbox on Send QRC20 tokens page. Pressing the “Enter” key after entering an amount on the Send to Contract Page Optional Amount textbox will highlight the amount but does not validate that amount.
Also, for the Amount textboxes, the increment/decrement control changes the amount of QTUM by 0.001 per click and for QRC20 tokens by 0.1 per click. Would 1.0 per click be more useful?
The text was updated successfully, but these errors were encountered: