fix: adjust WindowedFrame layout width

[wjyrich]

Changed Layout.preferredWidth from 362 to 365 to fix layout alignment issues
This minor width adjustment ensures proper UI element positioning and prevents visual glitches
The change maintains the overall layout structure while improving visual consistency

fix: 调整 WindowedFrame 布局宽度

将 Layout.preferredWidth 从 362 改为 365 以修复布局对齐问题
这个微小的宽度调整确保了 UI 元素的正确位置并防止视觉瑕疵
该更改保持了整体布局结构同时提高了视觉一致性

Pms: BUG-330553

Summary by Sourcery

Bug Fixes:

• Tweak Layout.preferredWidth from 362 to 365 in WindowedFrame.qml to resolve UI alignment glitches

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusted the Layout.preferredWidth in WindowedFrame.qml from 362 to 365 to resolve UI alignment issues and ensure visual consistency without altering the overall layout structure.

File-Level Changes

Change	Details	Files
Incremented the layout preferred width for WindowedFrame to fix alignment glitches.	Changed Layout.preferredWidth value from 362 to 365	qml/windowed/WindowedFrame.qml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: BLumia, robertkill, wjyrich

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• debian/deepin/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[deepin-ci-robot]

deepin pr auto review

我来审查这个代码变更：

这是一个简单的QML文件中的布局宽度调整变更，将Layout.preferredWidth从362改为365。这个变更很小，但我仍可以从几个方面进行分析：

1. 语法逻辑：

   • 语法正确，没有语法错误
   • 属性设置符合QML语法规范

2. 代码质量：

   • 变更过于简单且没有解释原因，建议添加注释说明为什么需要增加3个单位的宽度
   • 建议考虑使用命名常量而不是硬编码数值，例如可以定义为Layout.preferredWidth: Constants.standardWidth

3. 代码性能：

   • 这种简单的数值变更对性能没有明显影响
   • 布局计算可能会有微小的变化，但可以忽略不计

4. 代码安全：

   • 没有明显的安全问题
   • 建议验证这个宽度变化是否会影响其他依赖于固定宽度的元素或布局

改进建议：

1. 添加注释解释宽度变化的原因：

// 将宽度从362增加到365以适应新的设计规范
Layout.preferredWidth: 365

2. 考虑使用常量或配置值：

// 建议在Constants.js中定义标准宽度
Layout.preferredWidth: Constants.standardWidth

3. 如果这个宽度变化是为了适应特定内容，建议添加最小/最大宽度限制：

Layout.preferredWidth: 365
Layout.minimumWidth: 360
Layout.maximumWidth: 370

总的来说，这个变更本身很简单且安全，但为了提高代码质量和可维护性，建议采用上述改进措施。