Fix Spark Name dialog layout for Qt6

[levoncrypto]

No description provided.

[coderabbitai]

Walkthrough

This pull request refines the Spark name creation UI by adjusting layout constraints, widget sizing policies, and visual properties. Changes include adding stretch factors, enabling RichText rendering for fee messages, and configuring size constraints and word wrapping for balance warning elements.

Changes

Cohort / File(s)	Summary
Spark Name UI Layout Refinement src/qt/forms/createsparkname.ui	Adjusts horizontal layout stretch factors, sizePolicy, and minimumSize properties for fee and balance warning elements. Enables RichText formatting for feeTextLabel, reduces spacer dimensions in horizontalLayout_warning, and enables wordWrap with styling for balanceWarningLabel. Sets sizeConstraint to SetMinimumSize for improved layout behavior.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• Crash on Non HD wallets fix #1709: Complements this PR by adding C++ logic to manage createSparkNameButton visibility/state while this PR refines the underlying UI layout and warning label presentation.

Suggested reviewers

• psolstice
• levonpetrosyan93

Poem

🐰 A dash of polish, a stretch here, a squish there,
The warning label blooms with care,
RichText flows where fees declare,
Layout tightens, sizing fair,
UI sparkles through the air! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The pull request description is completely missing. The mandatory 'PR intention' section required by the template has not been provided.	Add a detailed PR description following the template, including what the PR is intended to do and what issue it solves.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately describes the main change: fixing the Spark Name dialog layout specifically for Qt6 compatibility, which aligns with the UI property adjustments in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sparkname_msg_fix

Tip

🧪 Unit Test Generation v2 is now available!

We have significantly improved our unit test generation capabilities.

To enable: Add this to your .coderabbit.yaml configuration:

reviews:
  finishing_touches:
    unit_tests:
      enabled: true

Try it out by using the @coderabbitai generate unit tests command on your code files or under ✨ Finishing Touches on the walkthrough!

Have feedback? Share your thoughts on our Discord thread!

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}