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

Bug with Controls:NumericUpDown when setting Maximum programaticaly #1885

Closed
ghost opened this issue Apr 14, 2015 · 3 comments
Closed

Bug with Controls:NumericUpDown when setting Maximum programaticaly #1885

ghost opened this issue Apr 14, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 14, 2015

I have a Flyout panel with some elements on it.

  1. ComboBox
  2. ComboBox
  3. NumericUpDown -> Maximum is set programaticaly based on value selected in 2. Minimum is set to 0 in xaml.

If I go and select a value in 1. then go select a value in 2. and go and click on any of the +- signs in 3. , they are disabled. I fix this by entering a number manualy, then going and clicking on another control (1. or 2.) then coming back to 3. Arrows are now finaly enabled. This doesn't happen if I set the Maximum only from XAML. I tried setting both in xaml and again in codebehind but issue still occurs

EDIT: I also tryied binding it from XAML to a int in codebehind, issue still occurs.

@punker76
Copy link
Member

punker76 commented Nov 9, 2015

@xxMUROxx can you look at this? thx

@michaelmairegger
Copy link
Contributor

@punker76 yes

@michaelmairegger
Copy link
Contributor

@ghost can you try following PR if this exception is present also there?
#2245

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants