microsoft / microsoft/terminal
Tray Icon feature improvements and follow-ups
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
This issue is mainly for me to keep track of what could/should/would be done to improve on the Tray Icon feature.
Current Tray Icon Behavior
Left-Click = Summon MRU window.
Right-Click = Open Context Menu.
Current Context Menu
________________
| Focus Terminal |
| -------------- | ______________________________
| Windows-> | |Window {ID} - <unnamed window>|
|________________| |Named Window 1 |
|Named Window 2 |
|______________________________|
Clicking on any of the Window items in the Windows submenu will summon that particular window.
What's to come?
"So close I can taste it" : things I'm prioritizing
- Summon only minimized windows
- Quit All
- Quit just the selected window
- Summon All
- Restore All to taskbar
- Create new Window
"Further away so I can't taste it yet" : nice to haves or may be a bit more involved.
- Get rid of the ugly Win32 menu and use WinUI's MenuFlyout
- Customize left-click on icon behavior
- Browse tab names of the selected window
- Custom actions in the context menu
- How to gel with
StartOnUserLoginsetting? - #10660
- #12933
- wasn't mentioned anywhere in #9274 shockingly, coulda swore we discussed this.
"Follow Ups from PRs":
- Make quake window dropdown duration not magic number.
- Settings should refer to Notification Area by correct name (not ‘tray’) #11101
References
#5727 - Initial Feature Request
#10368 - Initial Tray Icon PR
Tray Icon Spec Section
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Tray Icon Spec Section and the initial Tray Icon PR (#10368), then review the unchecked items to identify one focused follow-up. The issue does not name implementation files or tests, and completion criteria differ across the listed features, so a contributor should first narrow this into a specific task with maintainers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100