Skip to content

qt: remove leftover empty widget from Asset Info panel (#395)#455

Open
JSanchezFDZ wants to merge 1 commit into
Raptor3um:developfrom
JSanchezFDZ:fix/assetinfo-remove-empty-listwidget
Open

qt: remove leftover empty widget from Asset Info panel (#395)#455
JSanchezFDZ wants to merge 1 commit into
Raptor3um:developfrom
JSanchezFDZ:fix/assetinfo-remove-empty-listwidget

Conversation

@JSanchezFDZ

Copy link
Copy Markdown

Problem

The Assets dialog shows an empty box in the bottom-right of the Asset Info
area (most visibly on the Windows Qt build) — issue #395.

Root cause

src/qt/forms/assetsdialog.ui defines a QListWidget named listWidget that
is never populated or referenced from any source file. Its only traces are the
.ui definition and a dead QDialog#AssetsDialog QListWidget#listWidget rule in
general.css. Because it has a fixed minimumSize width of 380px and an
expanding size policy, it reserves space and renders as an empty widget.

Fix

Remove the orphan widget from the .ui and its dead stylesheet rule. Verified
that no code references listWidget (grep across src/qt), and the .ui
remains well-formed XML after the removal.

Closes #395.

The Assets dialog carried a `QListWidget` ("listWidget") in the bottom-right
of the Asset Info area that was never populated or referenced from any code —
its only traces were the .ui definition and a dead stylesheet rule. With a
fixed 380px minimum width it rendered as an empty box (most visibly on the
Windows Qt build).

Remove the orphan widget and its stylesheet rule. No code references it, so
nothing else changes.
@JSanchezFDZ JSanchezFDZ force-pushed the fix/assetinfo-remove-empty-listwidget branch from c8ac0eb to f0f9739 Compare June 22, 2026 15:08
@JSanchezFDZ

Copy link
Copy Markdown
Author

Hi @CodeIsTheKey @npq7721 @nandofw — when any of you have a moment (no rush), I'd appreciate a look at a small batch of focused fixes I've opened against develop. Each is one issue / one concern and closes the issue it references:

All are small and backward-compatible, and I've left ACKs on a few of the open community PRs too. Happy to squash, rebase, or adjust anything. Thanks for maintaining this.

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.

1 participant