fix(tray-tooltip): apply DTK t8 font to tray tooltips

[MyLeeJiEun]

1. Set SNI tray tooltip font to DFontManager t8 style
2. Re-apply the font on system font change via fontChanged signal
3. Use t8 font in TipsWidget paintEvent for dock tips

Log: Tray and dock tooltips now follow the DTK t8 font and update on font change
Influence: Tooltip text follows system font style and refreshes when fonts change

fix(tray-tooltip): 托盘提示使用 DTK t8 字体

1. SNI 托盘提示使用 DFontManager 的 t8 字体样式
2. 系统字体变化时通过 fontChanged 信号重新应用字体
3. TipsWidget 绘制时使用 t8 字体

Log: 托盘及 Dock 提示应用 DTK t8 字体，并随系统字体变化同步更新
PMS: BUG-375465
Influence: 提示文字跟随系统字体样式并随字体变化更新

Summary by Sourcery

Apply DTK T8 font styling to tray and dock tooltips and keep it synchronized with system font changes.

New Features:

• Apply the DTK T8 font style to SNI tray and dock tooltip text.

Bug Fixes:

• Ensure tray and dock tooltip fonts follow the system font style consistently.

Enhancements:

• Bind tooltip widgets to DTK font management so their typography updates automatically when system fonts change.

[deepin-ci-robot]

Hi @MyLeeJiEun. Thanks for your PR.

I'm waiting for a linuxdeepin member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates tray and dock tooltip rendering to use the DTK DFontManager t8 style, with SNI tray tooltips reapplying the font when system font settings change.

Sequence diagram for DTK tooltip font application and refresh

sequenceDiagram
    participant Tooltip as SNITrayTooltip
    participant FM as DFontManager
    participant System as SystemFontSettings

    Tooltip->>FM: t8()
    FM-->>Tooltip: Return DTK t8 font
    Tooltip->>Tooltip: setFont()
    FM-->>Tooltip: fontChanged()
    Tooltip->>FM: t8()
    FM-->>Tooltip: Return updated t8 font
    Tooltip->>Tooltip: setFont()

Loading

File-Level Changes

Change	Details	Files
Apply the DTK t8 font consistently to SNI tray tooltips and refresh it when the system font changes.	Obtain the t8 font from DFontManager when creating/accessing the tooltip. Subscribe to DFontManager::fontChanged and reapply the updated t8 font.	plugins/application-tray/sniprotocolhandler.cpp
Render dock tooltip text using the DTK t8 font.	Set the QPainter font from the application font manager before painting tooltip content. Add the required DTK GUI and font manager includes.	plugins/dde-dock/widgets/tipswidget.cpp

---

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 - I've found 2 issues

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="plugins/application-tray/sniprotocolhandler.cpp" line_range="252-260" />
<code_context>
+
+    const DFontManager *fm = DGuiApplicationHelper::instance()->fontManager();
+    m_tooltip->setFont(fm->t8());
+    connect(fm, &DFontManager::fontChanged, this, [this, fm] {
+        m_tooltip->setFont(fm->t8());
+    });

     if (!m_sniInter->toolTip().title.isEmpty()) {
</code_context>
<issue_to_address>
**nitpick (bug_risk):** `tooltip()` connects the same `fontChanged` signal every time it is called, even after `m_tooltip` already exists. `TrayPlugin::getToolTip()` calls `handler->tooltip()` twice and calls it again for every `NewToolTip`, so each font change invokes an ever-growing number of duplicate lambdas.

**Triggers:** When a tray item tooltip is refreshed or retrieved more than once before a system font change.

**Suggested fix:** Only establish the connection when creating `m_tooltip`, or use `Qt::UniqueConnection` with a persistent slot.

```suggestion
    const DFontManager *fm = DGuiApplicationHelper::instance()->fontManager();
    if (!m_tooltip) {
        const_cast<SniTrayProtocolHandler*>(this)->m_tooltip = new QLabel();
        m_tooltip->setForegroundRole(QPalette::BrightText);
        connect(fm, &DFontManager::fontChanged, this, [this, fm] {
            m_tooltip->setFont(fm->t8());
        });
    }

    m_tooltip->setFont(fm->t8());
```
</issue_to_address>

### Comment 2
<location path="plugins/dde-dock/widgets/tipswidget.cpp" line_range="85" />
<code_context>

     QPainter painter(this);
     painter.setPen(QPen(palette().brightText(), 1));
+    painter.setFont(Dtk::Gui::DGuiApplicationHelper::instance()->fontManager()->t8());

     QTextOption option;
</code_context>
<issue_to_address>
**issue (broader_impact):** `paintEvent()` draws with the DTK `t8` font, but `sizeHint()` and the multiline `lineHeight` calculation continue using the widget's inherited `fontMetrics()`. When those fonts have different metrics, the tooltip geometry is calculated for one font and painted with another, causing clipped text, incorrect spacing, or stale tooltip sizing.

**Triggers:** When the inherited widget font and `fontManager()->t8()` have different size or ascent/descent metrics.

**Suggested fix:** Store or apply the `t8` font to the widget before geometry calculations, and use metrics constructed from the same `t8` font in both `sizeHint()` and `paintEvent()`.
</issue_to_address>

---

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: mhduiy, MyLeeJiEun

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

[MyLeeJiEun]

/merge

[deepin-bot]

This pr cannot be merged! (status: blocked)

[MyLeeJiEun]

/forcemerge

[deepin-bot]

This pr force merged! (status: blocked)