Skip to content

fix(qt): correct updateWidth button check and banned node filter#2

Open
thepastaclaw wants to merge 2 commits intokwvg:data_txfrom
thepastaclaw:review/7144-data-tx
Open

fix(qt): correct updateWidth button check and banned node filter#2
thepastaclaw wants to merge 2 commits intokwvg:data_txfrom
thepastaclaw:review/7144-data-tx

Conversation

@thepastaclaw
Copy link

@thepastaclaw thepastaclaw commented Feb 17, 2026

Addresses review feedback from CodeRabbit on dashpay#7144:

1. updateWidth() — use isVisible() instead of isEnabled()

When setWalletActionsEnabled(false) disables toolbar buttons, they remain visible (greyed out) but updateWidth() was excluding them from the minimum-width calculation because it checked !isEnabled() || !isVisible(). This meant the window's minimum width no longer matched the visible button count. Changed to check only !isVisible() since width should track layout visibility, not enabled state.

2. Banned nodes with unknown ban time — return 1 instead of 0

The 'Hide Banned' filter in masternodelist.cpp checks status_value > 0. Banned nodes with no valid ban_height were returning 0 in EditRole, bypassing the filter. Changed to return 1 so these nodes are correctly hidden.


🤖 This was generated by an automated review bot.
Don't want automated PRs or comments on your code? You can opt out by replying here or messaging @PastaPastaPasta on Slack — we'll make sure the bot skips your PRs/repos going forward.

kwvg and others added 2 commits February 17, 2026 20:25
Proposals are made in the form of data transactions but look like oddly
shaped transactions in the UI, this should help better explain where the
proposal fee went.
- updateWidth: use isVisible() instead of isEnabled() for width
  calculation. Disabled-but-visible buttons should still contribute to
  the minimum window width since they occupy layout space.

- masternodemodel: return 1 instead of 0 for banned nodes with unknown
  ban time. The 'Hide Banned' filter checks status_value > 0, so
  returning 0 would let these nodes escape the filter.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments