-
Notifications
You must be signed in to change notification settings - Fork 3.6k
Fix RichProgressBar visibility #17532
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
Closed
Closed
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
f5232fc
updated the RichProgressBarTheme class for different terminals
ashikshafi08 d1f86d7
updated the RichProgressBarTheme class for different terminals
ashikshafi08 f67827c
updated the RichProgressBarTheme class for different terminals
ashikshafi08 87005de
updated the RichProgressBarTheme class for different terminals
ashikshafi08 a980032
updated the RichProgressBarTheme class for different terminals
ashikshafi08 4833118
updated the RichProgressBarTheme class for different terminals
ashikshafi08 5785548
updated the RichProgressBarTheme class for different terminals
ashikshafi08 056300a
updated the RichProgressBarTheme class for different terminals
ashikshafi08 a89bf5d
updated the RichProgressBarTheme class for different terminals
ashikshafi08 02f35ca
Merge branch 'Lightning-AI:master' into master
ashikshafi08 e64c3b5
[pre-commit.ci] auto fixes from pre-commit.com hooks
pre-commit-ci[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I want to know if this environment variable is set by the Terminal. My color system is 256 and I don't have this environment variable.
My idea is whether it's possible to have one solution that can adapt to two backgrounds, for example, not setting the colors of
default_description
anddefault_batch_progress
, will they be consistent with the default font color in different backgrounds, i.e., black in light theme and white in dark theme?Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But it may not be perfect in all cases, right? Especially if the user has a custom terminal theme with non-standard colors.
Also, what if we create a dictionary to store the default colors for each supported color system, so it makes it easy to add or modify the color settings accordingly?
Something like this,
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, what I mean is to use the
default
style fordescription
andbatch_progress
, which can avoid the problem of being invisible in light themes as mentioned in issue #17532.As I mentioned in #17532, from my perspective, the first 16 standard colors of most themes are carefully selected and suitable for the theme. So my idea is to only use them.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So the above code works?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so :), although I haven't tested it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
I will update the code and run some test cases, then make a PR again.