-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Move delete button theme resources into CommonResources.xaml #10454
Comments
Hi @miniksa @carlos-zamora, Can I work on this issue? As I'm quite new to open-source, I might need your guidance. |
@sourabh112 Go right ahead! |
Thanks @zadjii-msft , for the opportunity and sorry for late reply. I'm starting with making myself familiar with the code, so that my changes won't affect anything else. |
Hi |
Here's the link to changes made in CommonResource.xaml file. |
I will look at the PR. |
Some changes to the Settings UI: * Removed borders, made Settings use a single background * Updated color schemes buttons * Created DeleteButtonStyle based on accent button - closes #10454 ![image](https://user-images.githubusercontent.com/101892345/164984872-0fc75dc6-b4c0-4273-a2a6-b2b8a8d4d8ca.png)
Some changes to the Settings UI: * Removed borders, made Settings use a single background * Updated color schemes buttons * Created DeleteButtonStyle based on accent button - closes #10454 ![image](https://user-images.githubusercontent.com/101892345/164984872-0fc75dc6-b4c0-4273-a2a6-b2b8a8d4d8ca.png) (cherry picked from commit a7d2885) Service-Card-Id: 81805354 Service-Version: 1.13
🎉This issue was addressed in #12973, which has now been successfully released as Handy links: |
🎉This issue was addressed in #12973, which has now been successfully released as Handy links: |
There's a few places in the Settings UI where we have a "delete button":
We should move these over to CommonResources.xaml.
Examples of what this would look like:
terminal/src/cascadia/TerminalSettingsEditor/CommonResources.xaml
Lines 14 to 32 in b659321
If we have any other theme resources that we use in a few places, we should do the same. I'm also open to the idea of having a separate file named something like
CommonThemeResources.xaml
if we wanted to take that route.The text was updated successfully, but these errors were encountered: