Skip to content

feat: 内存数值悬停说明整机占用与专用工作集的区别 - #81

Merged
Ray-lea merged 6 commits into
Ray-lea:mainfrom
digital-bombyx:feat/memory-scope-hints
Nov 15, 2026
Merged

Ray-lea merged 6 commits into
Ray-lea:mainfrom
digital-bombyx:feat/memory-scope-hints

Conversation

@digital-bombyx

Copy link
Copy Markdown
Contributor

概况带的内存数值与百分比、进程表头“内存”列和分类标题的内存合计在悬停时分别说明各自的口径:概况带与表头百分比为整机已用物理内存,进程行、应用组与分类合计为专用工作集,并指向使用指南的“内存统计口径”。表头原先只说明行内的专用工作集,与其上方的整机百分比不符。对应路线图中的“内存口径提示”。

改动内容 / Changes

Implements the roadmap item "内存口径提示" (memory scope hints).

  • Overview band: the memory figure and its percentage get a tooltip saying it's whole-system physical memory in use (total minus available), and that process rows add up to less.
  • Process table: the "Memory" header tooltip now explains both numbers. The percentage above the label is system-wide usage; the rows show private working sets. Before, it only described the rows, which didn't match the figure above it.
  • Category headings (Apps / Background / Windows, and user groups): hovering the memory total says it's a sum of private working sets, and lists what whole-system usage adds on top.
  • All three point to "内存统计口径" in the user guide, which now mentions the tooltips. Texts in all 8 locales.

I left the roadmap entry as is, in case you'd rather tick or remove it yourself.

检查清单 / Checklist

  • 拉取请求标题与各个提交信息符合 Conventional Commits(<type>(<scope>): <描述>)/ The title and commit messages follow Conventional Commits
  • start.bat check 通过 / start.bat check passes — run as its parts (local Node is older than the pinned engine): i18n, cargo fmt, clippy -D warnings, Biome on locales/ and the UI tests pass
  • 行为变化已同步到 docs/ 中对应的页面 / Behavior changes are reflected in docs/
  • 文案已写入 locales/ 的中文与英文目录 / New text is in both the Chinese and English catalogs under locales/ (all 8 locales)
  • 界面改动附有截图,并按性能基线测量了开销 / UI changes include screenshots and a measurement against the performance baseline — screenshots attached; tooltip text only, no measurement
3333 22222222 11111

概况带的内存数值与百分比、进程表头“内存”列和分类标题的内存合计在悬停时分别说明各自的口径:概况带与表头百分比为整机已用物理内存,进程行、应用组与分类合计为专用工作集,并指向使用指南的“内存统计口径”。表头原先只说明行内的专用工作集,与其上方的整机百分比不符。
概况带卡片和进程表头的提示改为与表格单元格提示相同的换行方式,宽度 420 px,窗口未最大化时不再超出窗口;较短的提示仍为一行。
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 12, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-14T23:57:01.146497Z 7970a52 New commits
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 2a3a6fa73d

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread locales/en-US/processes.json Resolved
Comment thread docs/guide/README.md Resolved
使用指南只有简体中文版。中文与日文界面的提示改为引用其实际标题“内存统计口径”并注明指南为中文;其他语言的译文不能包含中文,改为不再引用指南,提示本身已说明两种口径的区别。路线图删除已完成的“内存口径提示”。

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 53eb4b2115

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread locales/en-US/processes.json Resolved
Comment thread locales/es-ES/processes.json Resolved
三条内存提示在所有语言中都指向使用指南:中文与日文引用其标题“内存统计口径”,其他语言给出文件路径 docs/guide/README.md 并注明为中文,分类合计的提示也补上指引。繁体中文、西班牙文与俄文改用目录中已有的专用工作集译名(專用工作集、Conjunto de trabajo privado、личный рабочий набор),与列说明一致。

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fa0b1f1ed1

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread locales/zh-CN/processes.json Resolved
digital-bombyx and others added 2 commits November 13, 2026 01:21
整机已用内存为总内存减去可用内存,备用缓存计入可用,不在其中。分类合计的提示改为“使用中的系统缓存”,与使用指南一致,避免与“性能 → 内存”的“已缓存”混淆。
@Ray-lea
Ray-lea merged commit bcf99ef into Ray-lea:main Nov 15, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants