microsoft / microsoft/PowerToys

Power Display: Tray icon redesign with per-monitor icons or assignable scroll target

Open
#48,321 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs-Triage Product-PowerDisplay
Dominant language
C
Stars
139k
Forks
8.6k
PR merge metrics
PR metrics pending

Description

Description of the new feature / enhancement

The current tray icon is a single generic white monitor glyph carrying no information. Two acceptable approaches, in order of preference:

  • Option A (preferred): one tray icon per monitor, each showing a large legible numeral, with scroll wheel support on each icon individually (see #48320).
  • Option B (fallback): keep a single tray icon, but allow the user to assign the scroll wheel target to a specific monitor in settings.
Scenario when this would be used?

With multiple monitors, the current single tray icon gives no indication of which display is being controlled. A per-monitor icon with a large numeral would make the active display immediately identifiable at a glance and enable direct per-monitor brightness control without opening the flyout. This is how Twinkle Tray handles it, and it significantly reduces interaction cost for multi-monitor setups.

Supporting information
  • Related feature request: #48320
  • Twinkle Tray (Microsoft Store)
  • ClickMonitorDDC implements per-monitor tray icons and scroll wheel on tray icon

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the current PowerToys tray icon behavior and related feature request #48320, then compare the referenced Twinkle Tray and ClickMonitorDDC behavior. Done means implementing and validating either per-monitor numbered tray icons with individual scroll targets or the fallback assignable scroll target in settings, with the chosen approach clearly documented.

Written by the indexing model from the issue text.

Assessment

Domain
desktop
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.