[IMPROVEMENT] Allow hiding the tray icon while keeping UniGetUI running in the background
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
首先跟踪现有的“Close UniGetUI to the system tray”设置，以及窗口关闭、托盘、后台更新、通知、重新打开和 Quit 流程。完成的标准是：后台检查可以在没有可见托盘图标的情况下继续，重新打开可以恢复窗口，显式的 Quit 仍然可用，并且现有默认值保持不变。
由索引模型根据 Issue 内容生成。
描述
Please confirm these before moving forward.
- I have searched for my feature proposal and have not found a work-in-progress/duplicate/resolved/discarded issue.
- This improvement refers to an existing feature.
- This improvement is not a bug.
Describe the improvement
Please separate system tray icon visibility from the behavior when closing the main window.
On Windows, I wanted to hide the tray icon while keeping UniGetUI running in the background. After disabling the existing Close UniGetUI to the system tray setting and closing the window, the application appears to exit instead.
Suggested independent settings:
- Keep UniGetUI running in the background when the window is closed.
- Show system tray icon.
With background operation enabled and the icon disabled, closing the window should leave background update checks running without a tray icon. Ideally, notifications should remain separately configurable where technically supported. If there are limitations, please explain them next to the setting.
Reopening UniGetUI from its normal shortcut should restore the existing window, and an explicit Quit command should remain accessible in the main UI. Existing defaults can remain unchanged.
This request is about hiding the icon entirely, not changing its theme or artwork (as in #4374 and #4838), nor merely moving it into Windows tray overflow.
Describe how this improvement could help users
Users could keep background update checking while reducing tray clutter. Separate controls would also make the settings clearer: window-close behavior and icon visibility are different preferences, but the current wording makes it difficult to discover whether they can be configured independently.
- 主要语言
- C#
- 星标
- 26.3k
- 派生
- 939
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 58
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Devolutions/UniGetUI 的其他 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 85/100
Devolutions/UniGetUI#5029 · 2 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 75/100
Devolutions/UniGetUI#4918 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 88/100
Devolutions/UniGetUI#4768 ·
维护者通常 1 天内回复
-
bug
难度 4/5 3-5 天 新手友好度 55/100
Devolutions/UniGetUI#5458 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 58/100
Devolutions/UniGetUI#5457 ·
维护者通常 1 天内回复
查看 Devolutions/UniGetUI 的全部 Issue
相似的 Issue
-
go 🏃 testing 🧪
难度 2/5 1-3 小时 新手友好度 78/100
valkey-io/valkey-glide#7239 ·
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
SubtitleEdit/subtitleedit#15462 ·
维护者通常 1 天内回复
-
:watch: Not Triaged
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
comp:instrumentation.aspnetcore
难度 2/5 1-3 小时 新手友好度 72/100
open-telemetry/opentelemetry-dotnet-contrib#5427 ·
维护者通常 1 天内回复
-
enhancement needs-triage pkg:OpenTelemetry
难度 2/5 1-3 小时 新手友好度 68/100
open-telemetry/opentelemetry-dotnet#7851 · 4 条评论 ·
维护者通常 1 天内回复