Skip to content

feat: improve tooltips for CPU and RAM modules#1142

Open
Times-Z wants to merge 2 commits intoJas-SinghFSU:masterfrom
Times-Z:feat/CPU-percore-usage
Open

feat: improve tooltips for CPU and RAM modules#1142
Times-Z wants to merge 2 commits intoJas-SinghFSU:masterfrom
Times-Z:feat/CPU-percore-usage

Conversation

@Times-Z
Copy link
Copy Markdown
Contributor

@Times-Z Times-Z commented Nov 28, 2025

This PR improve the CPU usage monitoring module to the bar with per-core usage display and the RAM usage with used/max tooltip

Features Added

1. CPU Usage Module

  • Added new CPU monitoring per core option for the tooltip
  • Added showPerCoreUsage configuration option
    When enabled, hovering over the module shows:
    • Individual usage percentage for each CPU core using stats from /proc/stat
    • Core numbering for easy identification
    • When disabled, shows simple overall CPU usage in tooltip
    • Respects the same rounding setting as the main display
screenshot_20251128_110412 screenshot_20251128_110531 screenshot_20251128_110558

2. RAM Usage Module

  • Improve the tooltip to show used / max current memory
screenshot_20251128_110458

return `Core ${index}: ${displayUsage}%`;
}).join('\n');

return `${coreLines}`;
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

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

Nit: We can remove the template literal.

Suggested change
return `${coreLines}`;
return coreLines;

@Jas-SinghFSU
Copy link
Copy Markdown
Owner

And a few linter errors, otherwise good. Thanks!

@Dieterbe
Copy link
Copy Markdown

Dieterbe commented Jan 5, 2026

This looks nice! Thank you!

What do you think of per-core visualization in the bar itself? (without needing to mouseover)
there are ways to do this in a compact way, see #1162 - i like how waybar implements it, although having the data in a tooltip achieves much of the same thing (albeit a bit less visually)

@Times-Z
Copy link
Copy Markdown
Contributor Author

Times-Z commented Jan 7, 2026

This looks nice! Thank you!

What do you think of per-core visualization in the bar itself? (without needing to mouseover) there are ways to do this in a compact way, see #1162 - i like how waybar implements it, although having the data in a tooltip achieves much of the same thing (albeit a bit less visually)

Maybe if I take the time I can implement this in next week end
Tbh it's doesn't seems to be a feature that will take a lot of time to implement

lika85456 added a commit to lika85456/HyprPanel that referenced this pull request Feb 3, 2026
@Times-Z Times-Z force-pushed the feat/CPU-percore-usage branch from 35d30c7 to cea4ca3 Compare February 7, 2026 16:41
@Times-Z
Copy link
Copy Markdown
Contributor Author

Times-Z commented Feb 13, 2026

Any news ?

@Times-Z Times-Z force-pushed the feat/CPU-percore-usage branch from cea4ca3 to 8b148d6 Compare March 23, 2026 08:56
@Times-Z Times-Z force-pushed the feat/CPU-percore-usage branch from 8b148d6 to b3a1a22 Compare March 23, 2026 21:54
@Dieterbe
Copy link
Copy Markdown

@Times-Z from one user/contributor to another, have you checked out https://github.com/wayle-rs/wayle ? it's the successor to hyprpanel and it's really good. probably makes more sense to start using that and spend your efforts there. we got some cool things in the works for (CPU) visualizations like wayle-rs/wayle#48 and wayle-rs/wayle#57

@Times-Z
Copy link
Copy Markdown
Contributor Author

Times-Z commented Mar 29, 2026

I’ve seen Wayle, but I prefer waiting for the stable release before migrating and contributing !

@Dieterbe
Copy link
Copy Markdown

fair enough, but FWIW i've found it to be surprisingly solid and polished even today.

@Times-Z
Copy link
Copy Markdown
Contributor Author

Times-Z commented Mar 30, 2026

I've migrate to wayle this night @Dieterbe !
Planned to contribute on the other side later, I look at the project now :)

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.

3 participants