sync: from linuxdeepin/dtkwidget

[deepin-ci-robot]

Synchronize source files from linuxdeepin/dtkwidget.

Source-pull-request: linuxdeepin/dtkwidget#596

[deepin-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: deepin-ci-robot

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

关键摘要:

• 在DIndeterminateProgressbar类的paintEvent方法中，使用setClipping方法可能会导致性能问题，因为它需要在每次绘制时检查和设置m_sliderWidget的边框。建议考虑其他方法来优化性能。
• DBounceAnimation类的bounceBack方法中，d->m_animationTarget->viewport()->geometry()的调用可能不是必要的，因为d->m_animationTarget是一个QWidget，它没有viewport()方法。应该检查d->m_animationTarget的类型和属性是否正确。
• DIndeterminateProgressbar类的resizeEvent方法中，d->m_sliderWidget->width() < d->m_spotWidget->width() / 2的检查逻辑可能存在问题，因为d->m_spotWidget->width()可能为0或负数，导致比较时出现错误。
• DIndeterminateProgressbar类的paintEvent方法中，clipPath.addRoundedRect(d->m_sliderWidget->geometry(), radius, radius);可能会导致性能问题，因为每次绘制时都添加了一个新的路径。建议在需要时创建路径，而不是在每次绘制时都添加。
• DBounceAnimation类的setAnimationTarget方法中，d->m_animationTarget = w;可能会导致悬空指针，因为d->m_animationTarget可能尚未初始化。应该在调用setAnimationTarget之前确保d->m_animationTarget已经被正确初始化。

是否建议立即修改:
是

[deepin-bot]

TAG Bot

New tag: 6.0.19
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #74

[deepin-bot]

TAG Bot

New tag: 6.0.21
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #81

[deepin-bot]

TAG Bot

New tag: 6.0.22
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #95

[deepin-bot]

TAG Bot

New tag: 6.0.23
DISTRIBUTION: unstable
Suggest: synchronizing this PR through rebase #96