Binding errors on screen load

Question

1.00/5 (1 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

Shahare

Updated 10-Dec-12 9:31am

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 10-Dec-12 17:50pm

Idea? Sure: provide some code sample.
--SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

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

Shahare · Accepted Answer · 2012-12-10T20:48:00

XML

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.