feat(renderer): allow plugin groups to override segment colors#202
Merged
fabioluciano merged 1 commit intofabioluciano:mainfrom Mar 6, 2026
Merged
Conversation
fabioluciano
approved these changes
Mar 5, 2026
Owner
|
All ok for me... i just ask you to add docs for this option before you merge it :) wiki/Configuration.md and wiki/assets/powerkit-options.conf |
endoze
force-pushed
the
allow-groups-to-color-built-in-widgets
branch
from
034cf95 to
ca95eea
Compare
Contributor
Author
|
@fabioluciano I've updated the docs to reflect my changes, have a look and see if this will work for you. |
Owner
|
Hi :) you need to resolve the conflict |
Currently plugin groups only affect separator background colors between grouped plugins, relying on health-based colors for the segments themselves. This makes groups less visually cohesive since each plugin still renders with its own health-derived palette. Adding a @powerkit_plugin_group_coloring option lets users opt into having the group palette color applied to all segments within a group, creating a unified visual band. Health feedback is preserved through bold text styling rather than background colors, so no information is lost. The feature is off by default to maintain backward compatibility. Special states (inactive, failed) and transparent mode are handled explicitly to avoid overriding semantic indicators that should always take precedence over cosmetic grouping.
endoze
force-pushed
the
allow-groups-to-color-built-in-widgets
branch
from
ca95eea to
fb3dd74
Compare
Contributor
Author
|
I've resolved the conflicts in both the main repo and the submodule |
github-actions bot
pushed a commit
that referenced
this pull request
Mar 6, 2026
## [5.24.0](v5.23.1...v5.24.0) (2026-03-06) ### Features * **renderer:** allow plugin groups to override segment colors ([#202](#202)) ([a5eb7a6](a5eb7a6))
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently plugin groups only affect separator background colors between grouped plugins, relying on health-based colors for the segments themselves. This makes groups less visually cohesive since each plugin still renders with its own health-derived palette.
Adding a @powerkit_plugin_group_coloring option lets users opt into having the group palette color applied to all segments within a group, creating a unified visual band. Health feedback is preserved through bold text styling rather than background colors, so no information is lost. The feature is off by default to maintain backward compatibility.
Special states (inactive, failed) and transparent mode are handled explicitly to avoid overriding semantic indicators that should always take precedence over cosmetic grouping.
Closes #201