qt-qml-attachments
Qt Qml Attachments
Overview
Fix and tune QML chat attachment layouts so chips/images wrap in rows, align to the correct side, preserve ordering, and keep message bubbles from stretching full width.
Quick Diagnosis
- If attachments stack vertically, the Flow likely has no usable width. Avoid binding
Flow.widthto its ownimplicitWidth. - If the row aligns left when it should align right, check
layoutDirection, anchors, and model order. - If bubbles appear full-width, clamp
Layout.preferredWidthand Flow width to a max ratio or fixed pixel cap.
Flow Width & Wrap
- Give
Flowan explicit width based on available space (e.g.,chatArea.width - margins). - Use
Math.max(0, ...)to avoid negative widths during resize. - For the container height, prefer
implicitHeightoverheightwhen it’s driven by a Flow.
Example:
More from bohdan-shulha/skills
commit-jira
Create and execute Git commits with a required JIRA-style subject and required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit and expects a ticket-prefixed subject. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
10claude-cli-agent-protocol
>-
10commit
Create and execute Git commits in Conventional Commits format with a required body. Use when the user asks to commit changes, write commit messages, or prepare a clean commit. Always run a pre-commit safety guard first, abort on log files or untracked high-risk binary extensions, then stage with `git add . -A`.
9plan-b
Create a concise plan for coding/build tasks, especially when users say "I want to make..." or "I need to do...". Use to generate a final plan by aggregating multiple subagent plan variants, include ASCII diagrams/flows/UI mockups when possible, and follow the create-plan style (read-only scan, minimal questions).
8repo-wiki
Generate and maintain a living repo wiki, specs, PRDs, and architecture docs in .repo-wiki/ so coding agents can navigate the codebase with strong context. Use for codebase discovery, PR-driven documentation updates, module docs, architecture maps, feature specs, and deleting stale knowledge when code changes.
1