NumericUpDown Control Throw Exception Error

Question

0.00/5 (No votes)

See more:

Just created a basic two NumericUpDown control in winform. These two controller do the increment and decrement of the value, like if i choose 5 in first controller the second controller automatically choose 6, the same way in decrement.

I have used this code:

VB

Private Sub NumericUpDown2_ValueChanged(sender As Object, e As EventArgs) Handles NumericUpDown2.ValueChanged
       NumericUpDown2.Minimum = NumericUpDown2.Value + 1
   End Sub

   Private Sub NumericUpDown3_ValueChanged(sender As Object, e As EventArgs) Handles NumericUpDown3.ValueChanged
       NumericUpDown3.Maximum = NumericUpDown3.Value - 1
   End Sub

Then when i run with F5, i got the exception error of "System.StackOverflowException occured in Project.exe file" , then when i click the Break button, it opened the Application.Designer.vb file and highlighting the code -

Me.MainForm = Global.ProjectLinked.PLGeneralSettings

Please help me..

Posted 1-Sep-15 22:21pm

Member 11927641

Add a Solution

Comments

Andy Lanng 2-Sep-15 4:32am

System.StackOverflowException occurs when you have a recursive method, or when you cause a recursive event. Is it possible that you have a control that contains itself? This would also be a recursion. Check your code to make sure that this isn't the case.

Also, the stacktrace might be more helpful finding the root cause

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)

OriginalGriff · Answer 1 · 2015-09-01T22:40:00

Solution 1

:sigh:
Look at your code.
In the ValueChanged event handler, you are changing the value of the minimum value to one greater than the current value - so that causes the control to change the value so it fits in the new limits. This causes another ValueChanged event to fire, where you...change the value again, causing another ValueChanged event, where you...
This continues until your app ruins out of space and falls over.

Don't do that. It's silly.

Posted 1-Sep-15 22:40pm

OriginalGriff

Comments

Member 11927641 2-Sep-15 4:42am

OMG... thanks for the advice.. I am a sh*t noob so i didn't knew that issues. Is there any tutorial to do the same without type of problem because i didn't find the same anywhere.?

OriginalGriff 2-Sep-15 5:03am

No - you can't do that because it's logically silly! You are trying to set the Value property outside the range of valid values, and the control won't let you do that. That's part of the reason for using a NumericUpDown control - the Value is always valid and within range.