Bitcoin-Qt: never display own block count > estimated block count
- some users reported it as weird, that the estimated block count could be lower than our own nodes block number (which is indeed true and not good) - this pull adds a new default behaviour, which displays our own block number as estimated block number, if own >= est. block count - the pull raises space for nodes block counts in cPeerBlockCounts to 8 to be more accurate - also removes a reduntant setNumBlocks() call in RPCConsole and moves initialisation of numBlocksAtStartup in ClientModel, where it belongs
This commit is contained in:
@@ -269,8 +269,6 @@ void RPCConsole::setClientModel(ClientModel *model)
|
||||
|
||||
setNumConnections(model->getNumConnections());
|
||||
ui->isTestNet->setChecked(model->isTestNet());
|
||||
|
||||
setNumBlocks(model->getNumBlocks(), model->getNumBlocksOfPeers());
|
||||
}
|
||||
}
|
||||
|
||||
@@ -342,13 +340,10 @@ void RPCConsole::setNumConnections(int count)
|
||||
void RPCConsole::setNumBlocks(int count, int countOfPeers)
|
||||
{
|
||||
ui->numberOfBlocks->setText(QString::number(count));
|
||||
ui->totalBlocks->setText(QString::number(countOfPeers));
|
||||
// If there is no current countOfPeers available display N/A instead of 0, which can't ever be true
|
||||
ui->totalBlocks->setText(countOfPeers == 0 ? tr("N/A") : QString::number(countOfPeers));
|
||||
if(clientModel)
|
||||
{
|
||||
// If there is no current number available display N/A instead of 0, which can't ever be true
|
||||
ui->totalBlocks->setText(clientModel->getNumBlocksOfPeers() == 0 ? tr("N/A") : QString::number(clientModel->getNumBlocksOfPeers()));
|
||||
ui->lastBlockTime->setText(clientModel->getLastBlockDate().toString());
|
||||
}
|
||||
}
|
||||
|
||||
void RPCConsole::on_lineEdit_returnPressed()
|
||||
|
||||
Reference in New Issue
Block a user