Skip to content

fix(display): adjust default manual color temperature#1107

Merged
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
52cyb:master
May 15, 2026
Merged

fix(display): adjust default manual color temperature#1107
deepin-bot[bot] merged 1 commit into
linuxdeepin:masterfrom
52cyb:master

Conversation

@52cyb
Copy link
Copy Markdown
Contributor

@52cyb 52cyb commented May 15, 2026

The default value for manual color temperature mode was 3500K which caused unexpected warm tint when users first enable color temperature. Change to 6500K to match the standard display default and the none-mode behavior.

手动模式下默认色温值为3500K,修改为6500K,与标准显示器默认值保持一致。

Log: 修正手动色温默认值为6500K
PMS: 360915
Influence: 控制中心开启护眼模式,全天模式下,默认色温为50%

Summary by Sourcery

Adjust the default manual color temperature configuration to align with the standard display default and non-adjusted mode behavior.

Bug Fixes:

  • Correct the initial manual color temperature value to prevent an unexpectedly warm tint when enabling color temperature adjustment.

Enhancements:

  • Update display configuration so manual color temperature defaults to a neutral 6500K matching typical display settings.

The default value for manual color temperature mode was 3500K which caused unexpected warm tint when users first enable color temperature. Change to 6500K to match the standard display default and the none-mode behavior.

手动模式下默认色温值为3500K,修改为6500K,与标准显示器默认值保持一致。

Log: 修正手动色温默认值为6500K
PMS: 360915
Influence: 控制中心开启护眼模式,全天模式下,默认色温为50%
@deepin-ci-robot
Copy link
Copy Markdown

Hi @52cyb. 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
Copy link
Copy Markdown

sourcery-ai Bot commented May 15, 2026

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adjusts the default manual color temperature value to align with standard display behavior and the non-manual mode default.

File-Level Changes

Change Details Files
Update the default manual color temperature from a warm 3500K to a neutral 6500K to match standard display defaults and non-manual behavior.
  • Change the configuration value used as the default color temperature in manual mode from 3500K to 6500K
  • Ensure that when users first enable manual color temperature (e.g., in eye-protection/全天 mode), the slider starts at the neutral 6500K value instead of an unexpectedly warm tint
misc/dsg-configs/org.deepin.Display.json

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

Copy link
Copy Markdown

@sourcery-ai sourcery-ai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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


Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

@deepin-ci-robot
Copy link
Copy Markdown

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: 52cyb, fly602

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

Details Needs approval from an approver in each of these files:

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

@52cyb
Copy link
Copy Markdown
Contributor Author

52cyb commented May 15, 2026

/forcemerge

@deepin-bot
Copy link
Copy Markdown
Contributor

deepin-bot Bot commented May 15, 2026

This pr force merged! (status: unstable)

@deepin-bot deepin-bot Bot merged commit 8184e7d into linuxdeepin:master May 15, 2026
16 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants