-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
People think the Color Scheme editor will change the current colors #9775
Comments
What terminal version. |
I'm seeing this issue as well. Just updated to v1.7.1033.0 (the new release). No matter what I try, I can't seem to apply a color scheme using the new Settings UI. It gets reset back to Campbell on each relaunch. Edit: This issue with with the default color scheme. Changing the scheme under individual profiles does apply the scheme properly to that profile. Edit 2: Looking at recent commits, looks like it might be fixed in #9764 |
Same issue. Version: 1.7.1033.0 |
@zadjii-msft You're totally correct, now that I've taken a look into that. Gotta say though, it's definitely confusing on first use. I would assume that the Color schemes page is for selecting a default color scheme for all profiles (and yes you could edit the colors as well). Then you can go into individual profiles and override to a different color scheme. Perhaps it just needs some some clarification on what the Coloring schemes page does. Maybe selecting a default color scheme would be better suited under Appearance (if setting a default color scheme is a goal). |
Is it possible to change default theme that would apply to all profiles like via settings.json? |
/cc @cinnamon-msft |
I'll make sure to pass that feedback along to the UI designers (and my "I" I mean @cinnamon-msft 😋) I'll close the rest of this discussion about setting the default for all profiles as a /duplicate of #9539 - we're generally having that discussion in that thread. |
Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report! |
People get confused about this. This should help. It doesn't really fix it, but it should help. * [x] Does enough for #9775 to get it out of 1.14 * [x] I work here * [x] Screenshot below. ![image](https://user-images.githubusercontent.com/18356694/157732913-86f0af51-8c37-4827-9d21-5775d0bfdeb7.png) * [ ] todo: Discuss the text here. @cinnamon-msft this sound good?
People get confused about this. This should help. It doesn't really fix it, but it should help. * [x] Does enough for #9775 to get it out of 1.14 * [x] I work here * [x] Screenshot below. ![image](https://user-images.githubusercontent.com/18356694/157732913-86f0af51-8c37-4827-9d21-5775d0bfdeb7.png) * [ ] todo: Discuss the text here. @cinnamon-msft this sound good?
People get confused about this. This should help. It doesn't really fix it, but it should help. * [x] Does enough for #9775 to get it out of 1.14 * [x] I work here * [x] Screenshot below. ![image](https://user-images.githubusercontent.com/18356694/157732913-86f0af51-8c37-4827-9d21-5775d0bfdeb7.png) * [ ] todo: Discuss the text here. @cinnamon-msft this sound good? (cherry picked from commit 460a991)
Punting this for a release, since we feel like this wasn't wholly addressed in #13269 |
Update the color schemes page with the new Win 11 style. With the rejuvenated experience, we now have two pages: - `ColorSchemes.xaml`: "color scheme selection" page - This is the starting page for the "color schemes" nav view item. It is intended to have the user select a color scheme they want to modify. The user can also click the "Add new" button to add a new color scheme or the "delete" button to delete the selected scheme. - If a scheme cannot be deleted, the delete button is disabled and a disclaimer is shown. - A "set as default" button sets the selected scheme as the color scheme for profiles.default (aka "base layer"). - The list view item for each scheme includes the name of the scheme, the default tag (if the scheme is the one set in base layer), a text preview of the foreground/background, and a grid of 16 color chips showing the colors for the scheme. - Implementation details: - View - `ColorSchemes`: - "Enter" --> edit the selected scheme - "Delete" --> delete the selected scheme - if the selected scheme cannot be deleted, we show the disclaimer - View model - `ColorSchemesPageViewModel` - when possible, the XAML binds directly to the view model functions. Thus, we include logic to delete, edit, and set the selected scheme as default. - store the current page, so that we know which page to navigate to upon saving/discarding changes. - `EditColorScheme.xaml`: "color scheme modification" page - a terminal preview of the color scheme is shown at the top of the page. - all colors for the scheme are displayed as color chips in an expander that starts as expanded. - renaming a color scheme is also inside an expander, but there's no need for "renaming mode" anymore - Implementation details: - View - `EditColorScheme`: - include logic to display the disclaimer and add the automation properties - include logic for "Enter" and "Escape" in the rename editor - View Model - `ColorSchemeViewModel`: - as before, when possible, the XAML binds directly to the view model functions. - To enable the "default" tag functionality, we had to expose knowledge of being the default via "IsDefaultScheme()" which compares the current name to the one in the settings model. - Miscellaneous implementation details: - to get the expander to start as expanded, we had to modify the setting container style. - Since "set as default" is a button on the selector page, we needed a way to refresh the view model's knowledge of being the default. So we added a `RefreshIsDefault` API to the `ColorSchemeViewModel` to notify changes. - With the new layout, we no longer need an 'enter rename mode' button, so all that logic has been removed - Add logic to `MainPage` to handle navigating to the correct page upon saving/discarding changes. Closes #9775 Co-authored-by: Carlos Zamora <cazamor@microsoft.com>
🎉This issue was addressed in #13269, which has now been successfully released as Handy links: |
Windows Terminal version (or Windows build number)
10.0.21354 (Dev)
Other Software
No response
Steps to reproduce
Expected Behavior
No response
Actual Behavior
Color Scheme.
The text was updated successfully, but these errors were encountered: