Click here to Skip to main content
13,199,852 members (71,895 online)
Rate this:
Please Sign up or sign in to vote.
See more:
Hi all

I'm using IntegerUpDown from the WPF toolkit and I'm binding the minimum, maximum, and value properties.

When the view loads, some of the values in the IntegerUpDown control display "0" (invalid input which I can't touch) even though the minimum is set via the binding to "1" (I can't touch this either).

Why does this happens?
Why doesn't the minimum enforces the minimum check on screen load?
When I scroll down the view probably refreshes as then the app crashes.

Any idea on this issue will be great

Note: The data is received from a server which can communicate with a parent application where in some cases this value is valid. I hope if I'll know what is causing this I'll know how to solve this the "right" way.
Posted 10-Dec-12 4:00am
Updated 10-Dec-12 9:31am
Sergey Alexandrovich Kryukov 10-Dec-12 17:50pm
Idea? Sure: provide some code sample.

1 solution

Rate this: bad
Please Sign up or sign in to vote.

Solution 1

I ran a test:
I added a converter to each property and found that the order of the properties
when writing the control in xaml is the order how they are bound.
My control was written as follow:
    <toolkit:IntegerUpDown Value="binding" Min="binding" Max="binding"/>
Once I inverted the order of the properties as follow:
    <toolkit:IntegerUpDown Min="binding" Max="binding" Value="binding"/>
The screen crashes on load as expected.
Hope this helps.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

  Print Answers RSS
Top Experts
Last 24hrsThis month

Advertise | Privacy |
Web01 | 2.8.171020.1 | Last Updated 11 Dec 2012
Copyright © CodeProject, 1999-2017
All Rights Reserved. Terms of Service
Layout: fixed | fluid

CodeProject, 503-250 Ferrand Drive Toronto Ontario, M3C 3G8 Canada +1 416-849-8900 x 100