From 8a33f4d63f9944f4877b3e2814b1582e72ceaa71 Mon Sep 17 00:00:00 2001 From: Luke Dashjr Date: Thu, 11 Apr 2019 23:44:48 +0000 Subject: GUI: Options: Remove the upper-bound limit from pruning size setting Hypothetically, someone may wish to begin pruning at a future blockchain size, and there's no reason to limit it lower --- src/qt/optionsdialog.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/qt') diff --git a/src/qt/optionsdialog.cpp b/src/qt/optionsdialog.cpp index 64e6f28ab2..fd42fd494c 100644 --- a/src/qt/optionsdialog.cpp +++ b/src/qt/optionsdialog.cpp @@ -150,7 +150,7 @@ void OptionsDialog::setModel(OptionsModel *_model) // Prune values are in GB to be consistent with intro.cpp static constexpr uint64_t nMinDiskSpace = (MIN_DISK_SPACE_FOR_BLOCK_FILES / GB_BYTES) + (MIN_DISK_SPACE_FOR_BLOCK_FILES % GB_BYTES) ? 1 : 0; - ui->pruneSize->setRange(nMinDiskSpace, _model->node().getAssumedBlockchainSize()); + ui->pruneSize->setRange(nMinDiskSpace, std::numeric_limits::max()); QString strLabel = _model->getOverriddenByCommandLine(); if (strLabel.isEmpty()) -- cgit v1.2.3