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

Fix IsReadonly issue #1840

Merged
merged 1 commit into from
Apr 15, 2015
Merged

Fix IsReadonly issue #1840

merged 1 commit into from
Apr 15, 2015

Conversation

michaelmairegger
Copy link
Contributor

[Fix] If in NumericUpDown the property IsReadOnly is set to true, then changing the values by clicking + and - Buttons is still possible
As you can see in https://github.com/MahApps/MahApps.Metro/blob/master/MahApps.Metro/Themes/NumericUpDown.xaml#L120 the only that disables the change of the value is the Trigger. Now even if the Style is customized and this kind of Trigger is not set, then the Change of value is not possible.

[Fix] If in NumericUpDown the property IsReadOnly is set to true, then changing the values by clicking + and - Buttons is still possible
As you can see in https://github.com/MahApps/MahApps.Metro/blob/master/MahApps.Metro/Themes/NumericUpDown.xaml#L120 the only that disables the change of the value is the Trigger. Now even if the Style is customized and this kind of Trigger is not set, then the Change of value is not possible.
punker76 added a commit that referenced this pull request Apr 15, 2015
@punker76 punker76 merged commit f484271 into MahApps:master Apr 15, 2015
@michaelmairegger michaelmairegger deleted the patch-1 branch April 16, 2015 09:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants