The commit 7066e8996d0ac090535cc97cdcb54a219986460f from #765 breaks “Open Wallet”, “Close Wallet” and “Close All Wallets” items in the File menu (at least on Ubuntu 23.10 + Wayland).
Reverting it to avoid this regression in the 26.0 release.
The commit 7066e8996d0ac090535cc97cdcb54a219986460f from #765 breaks “Open Wallet”, “Close Wallet” and “Close All Wallets” items in the File menu (at least on Ubuntu 23.10 + Wayland).
Reverting it to avoid this regression in the 26.0 release.
This reverts commit 7066e8996d0ac090535cc97cdcb54a219986460f.
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.
See the guideline for information on the review process.
If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.
m_wallet_controller
is null when the events are connected (at widget creation time). We need to move the connection to setWalletController()
, otherwise there is also a possible crash that could arise when any of these events is triggered prior to the wallet controller is set.
Upps.. it is because m_wallet_controller is null when the events are connected (at widget creation time). We need to move the connection to setWalletController(), otherwise there is also a possible crash that could arise when any of these events is triggered prior to the wallet controller is set.
So this isn’t actually platform specific, it was just always broken?
Upps.. it is because m_wallet_controller is null when the events are connected (at widget creation time). We need to move the connection to setWalletController(), otherwise there is also a possible crash that could arise when any of these events is triggered prior to the wallet controller is set.
So this isn’t actually platform specific, it was just always broken?
Since #765 merge, last week. Yes. It tell us how much we need to improve the GUI test coverage (and its code structure..). We fixed an issue and broke something else.