init: Fix crash due to -litemode and improve its deprecation warning #3626
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this PR the signal
CClientUIInterface::ThreadSafeMessageBox
is not connected to a slot in Qt at the time its emitted when-litemode
is used. The signal gets emitted fromInitWarning
, inInitParameterInteraction
. This happens currently beforeBitcoinGUI
gets created byapp.createWindow(networkStyle.data())
indash.cpp
where the signal becomes connected to the slot. After this commit the litemodeInitWarning
will be called inAppInitParameterInteraction
which runs afterBitcoinGUI
has been created, means the signal will be connected then at that point and the crash introduced in #3579 is fixed.This also brings some changes to the deprecation warning message if
-litemode
is still used.-litemode
gets used no matter if itsactivated or not.
-disablegovernance
gets forced by-litemode
.