Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: themeable HighlightingManager #46

Merged
merged 3 commits into from
Jan 31, 2025

Conversation

gerhardol
Copy link
Member

  • The default environment is set as static, so it can be updated by GitExtensions with theme colors.
    Any overrides in the actual themes would still be overriding the default environment colors (the theme overrides were recently removed though).

  • Make it possible to set colors as adaptable, to control if they should be adapted for the themes or not.
    Highlight colors hardcoded in the interface or in .xshd files (unless they are system colors)
    should generally be adapted, but colors in themes are likely to be set to the intended color.

* The default environment is set as static, so it can be
updated by GitExtensions with theme colors.
Any overrides in the actual themes would still be overriding the default
environment colors (the theme overrides were recently removed though).

* Make it possible to set colors as adaptable, to control if they should
be adapted for the themes or not.
Highlight colors hardcoded in the interface or in .xshd files
(unless they are system colors)
should generally be adapted, but colors in themes are likely to be
set to the intended color.
Copy link
Member

@mstv mstv left a comment

Choose a reason for hiding this comment

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

just nits

* The default environment is set as static, so it can be
updated by GitExtensions with theme colors.
Any overrides in the actual themes would still be overriding the default
environment colors (the theme overrides were recently removed though).

* Make it possible to set colors as adaptable, to control if they should
be adapted for the themes or not.
Highlight colors hardcoded in the interface or in .xshd files
(unless they are system colors)
should generally be adapted, but colors in themes are likely to be
set to the intended color.
mstv
mstv previously approved these changes Jan 26, 2025
@mstv mstv dismissed their stale review January 26, 2025 19:52

Another newline at eof was removed. Check editor settings [file]?

* The default environment is set as static, so it can be
updated by GitExtensions with theme colors.
Any overrides in the actual themes would still be overriding the default
environment colors (the theme overrides were recently removed though).

* Make it possible to set colors as adaptable, to control if they should
be adapted for the themes or not.
Highlight colors hardcoded in the interface or in .xshd files
(unless they are system colors)
should generally be adapted, but colors in themes are likely to be
set to the intended color.
@gerhardol
Copy link
Member Author

Another newline at eof was removed. Check editor settings [file]?

This project uses \n and MS VS constantly trashes the newlines.
I should be scripting this.

@gerhardol gerhardol merged commit 1cb6d9c into gitextensions:master Jan 31, 2025
2 checks passed
@gerhardol gerhardol deleted the feature/dark-mode branch January 31, 2025 20:56
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