docs(rules): document two Qt/QML gotchas in qt-app.md#80
Merged
Conversation
The navigation-shell work surfaced two non-obvious Qt/QML traps that cost real iteration: nested Layouts default fillWidth/fillHeight to true (a fixed-size rail expands and starves siblings unless pinned explicitly), and the offscreen test platform never delivers synthetic mouse events to Controls (drive components via public API or direct signal emission). Codifying both in qt-app.md so the next agent does not rediscover them. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Overview
The navigation-shell session surfaced two non-obvious Qt/QML traps that cost real iteration and weren't yet captured in
.claude/rules/qt-app.md. Codifying them turns session friction into durable guidance so the next agent touching the Qt app doesn't rediscover them.The two lessons:
fillWidth/fillHeightto true. ALayoutnested directly inside anotherLayout(e.g. aColumnLayoutrail inside aRowLayout) defaults these to true — unlike plain Items/controls, which default false — so a fixed-size rail expands and starves its siblings unless pinned explicitly. Documented under a new## Qt Quick Layoutssection.mouseClick()on aButtonfires nothing underQT_QPA_PLATFORM=offscreen; drive components via public API or direct signal emission instead. Documented as anOffscreen inputbullet alongside the existing test-harness conventions.Both are generic Qt/QML behavior in plain English, with no private or personal-environment references.