Skip to content

Conversation

@feinstein
Copy link
Contributor

What changed?

Fixed the HasDecimals property. It was broken on commit bd6aa38 which made the property stop working and decimals like ',' '.' were available when HasDecimals = false.

closes issue #2403.

@feinstein feinstein changed the title Fixes the HasDecimals property, broken before on commit #bd6aa38e. Fixes the HasDecimals property, broken before on commit bd6aa38e. Mar 7, 2016
punker76 added a commit that referenced this pull request Mar 8, 2016
Fixes the HasDecimals property, broken before on commit bd6aa38.
@punker76 punker76 merged commit 0be25ad into MahApps:master Mar 8, 2016
@punker76
Copy link
Member

punker76 commented Mar 8, 2016

@feinstein 👍

@punker76
Copy link
Member

punker76 commented Mar 8, 2016

@feinstein Please make the next PR on dev branch, thx.

@feinstein
Copy link
Contributor Author

@punker76 OK! Sorry, I thought since this was fix, and not a new feature to be developed, it should go straight to master.

@punker76
Copy link
Member

punker76 commented Mar 9, 2016

@feinstein you're normaly right, but I'm focused on finishing 1.3.0

@feinstein feinstein deleted the Fix-NumericUpDown-HasDecimals branch March 9, 2016 23:29
@feinstein
Copy link
Contributor Author

Ok, got it!

@punker76 I have been thinking on adding a feature to block the e to denote scientific notation, making the NumericUpDown only being able to receive plain numbers from the keyboard....should I go for this to 1.3.0?

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