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.

Sign up for GitHub

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

Jump to bottom

how to prevent the repeat button being change by other theme/lib #59

Open
heartacker opened this issue Apr 26, 2023 · 3 comments · May be fixed by #60
Open

how to prevent the repeat button being change by other theme/lib #59

heartacker opened this issue Apr 26, 2023 · 3 comments · May be fixed by #60

Comments

@heartacker
Copy link
Contributor

hi, I am using your NumericUpDownLib and also using other UI/THEME lib in my APP,
when I add those theme resource, the button style was change,

and how can we prevent this?

Thanks

image
@heartacker
Copy link
Contributor Author

heartacker commented Apr 27, 2023 •
edited
Loading

👯

heartacker added a commit to heartacker/NumericUpDownLibEx that referenced this issue Apr 27, 2023
@heartacker
fix Dirkster99#59
71af1ba
heartacker added a commit to heartacker/NumericUpDownLibEx that referenced this issue May 6, 2023
@heartacker
fix Dirkster99#59
686e704
@faguetan
Copy link

faguetan commented May 8, 2023

I had the same issue when using Material Design In XAML package. The solution (more of a crutch, tbh) is to use the NumericUpDownLib from GitHub in your project and then to set the Style property for RepeatButton in NumericRepeatButtonControl.xaml to {x:Null}. This prevented Material Design In XAML to sneak in and set the RepeatButton style. I also posted this question in Material Design In XAML repository (presuming that this behavior might break certain custom-made controls that we can install from NuGet and a mechanism to prevent carpet-bombing styling would be appreciated), but as of now, no answer yet.

@heartacker
Copy link
Contributor Author

yes, I had a pr #60 @faguetan

@heartacker heartacker linked a pull request May 14, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix #59 heartacker/NumericUpDownLibEx
2 participants
@heartacker @faguetan