Since cfe77ef41 the global nTxConfirmTarget wasn’t being updated by the smart fee slider and thus the coin control dialog and labels were not being updated.
I’m not sure this is the ideal way to pass this information around, I’m open to suggestions.
Since cfe77ef41 the global nTxConfirmTarget wasn’t being updated by the smart fee slider and thus the coin control dialog and labels were not being updated.
I’m not sure this is the ideal way to pass this information around, I’m open to suggestions.
821@@ -822,6 +822,12 @@ void SendCoinsDialog::coinControlUpdateLabels()
822 // set pay amounts
823 CoinControlDialog::payAmounts.clear();
824 CoinControlDialog::fSubtractFeeFromAmount = false;
825+ if (ui->radioSmartFee->isChecked()) {
826+ CoinControlDialog::coinControl->nConfirmTarget = ui->sliderSmartFee->maximum() - ui->sliderSmartFee->value() + 2;
Since cfe77ef41 the global nTxConfirmTarget wasn't being updated by the smart
fee slider and thus the coin control dialog and labels were not being updated.
@morcos As far as I see, 0.14.2 is not tagged, so you are still free to fixup the release notes. Just make sure to ping wumpus on irc when you have opened the pull.
I haven’t looked at the code, but if this is just a display issue, it is probably fine to only mention in the release notes. If this is actually ignoring the value from the slider, and users that chose a slow confirm target are effectively overpaying, we should hold back 0.14.2 for a few days.
On Wed, Jun 14, 2017 at 4:35 PM, Alex Morcos notifications@github.com wrote:
@laanwj https://github.com/laanwj is it too late to change release notes for 0.14.2? do you think it’s at least worth mentioning that it is a known bug. might save some people some confusion?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/pull/10582#issuecomment-308450949, or mute the thread https://github.com/notifications/unsubscribe-auth/AGGmv1uHYI_4EZpOeGA28bhh1dcIbZ_Zks5sD--5gaJpZM4N5AZe .
@MarcoFalke yes, just display
opened #10588