7 Answers, 1 is accepted
0
Hello Aicha,
We were able to reproduce the issue only while debugging.
The event is triggered only once when you change the value in the control via typing in the textbox or clicking the arrows. But when you place a breakpoint in the event it is hit multiple times. This is a common issue in some events which causes the breakpoints to be hit multiple times and at the same time behave as expected when not in debug mode. This issue may be caused by the focus getting reset to the control or another related scenario.
I would recommend to you to debug this and any other events in which you experience this issue with for example Debug.WriteLine() method without explicitly placing breakpoints in the event.
Hope this information is helpful.
Kind regards,
Vladi
the Telerik team
We were able to reproduce the issue only while debugging.
The event is triggered only once when you change the value in the control via typing in the textbox or clicking the arrows. But when you place a breakpoint in the event it is hit multiple times. This is a common issue in some events which causes the breakpoints to be hit multiple times and at the same time behave as expected when not in debug mode. This issue may be caused by the focus getting reset to the control or another related scenario.
I would recommend to you to debug this and any other events in which you experience this issue with for example Debug.WriteLine() method without explicitly placing breakpoints in the event.
Hope this information is helpful.
Kind regards,
Vladi
the Telerik team
Explore the entire Telerik portfolio by downloading Telerik DevCraft Ultimate.
0
kity
Top achievements
Rank 2
answered on 06 Feb 2014, 11:26 AM
Confirm too.
0
kity
Top achievements
Rank 2
answered on 06 Feb 2014, 12:19 PM
confirm too
http://www.telerik.com/forums/radnumericupdown---why-bug
http://www.telerik.com/forums/radnumericupdown---why-bug
0
kity
Top achievements
Rank 2
answered on 06 Feb 2014, 12:34 PM
May be you have biding twoway+codebehind logic update.
set biding ot OneTime mode
set biding ot OneTime mode
0
Hi,
As previously mentioned the event is correctly triggered only once if there is not break points inside the event handler. This is a common issue with some events which rely on the focus in order to be triggered and when there is a break point inside them the focus is moved and may cause multiple unexpected triggers.
I recorded a short video showing how the event is triggered only once when clicking the Up or down arrows.
Regards,
Vladi
Telerik
As previously mentioned the event is correctly triggered only once if there is not break points inside the event handler. This is a common issue with some events which rely on the focus in order to be triggered and when there is a break point inside them the focus is moved and may cause multiple unexpected triggers.
I recorded a short video showing how the event is triggered only once when clicking the Up or down arrows.
Regards,
Vladi
Telerik
Check out the new Telerik Platform - the only modular platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native apps. Register for the free online keynote and webinar to learn more about the Platform on Wednesday, February 12, 2014 at 11:00 a.m. ET (8:00 a.m. PT).
0
Rob Ainscough
Top achievements
Rank 1
answered on 03 Aug 2015, 04:32 PM
I can confirm the problem still exists in 2015 Q1. Has this issue been fixed in 2015 Q2 release or are you saying there is NO fix?
Debugging is an important part of the development process, so it's not acceptable to suggest a developer NOT place a breakpoint in event code.
Cheers, Rob.
0
Hi Rob,
Thank you for contacting us.
As this thread is a bit old could you give us some additional details about the exact scenario in which you experience the multiple ValueChanged event hits. This will help us make sure we are investigating the correct scenario and possibly provide a solution of any related issues.
Looking forward to your response.
Regards,
Vladi
Telerik
Thank you for contacting us.
As this thread is a bit old could you give us some additional details about the exact scenario in which you experience the multiple ValueChanged event hits. This will help us make sure we are investigating the correct scenario and possibly provide a solution of any related issues.
Looking forward to your response.
Regards,
Vladi
Telerik
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Explore the
Telerik Feedback Portal
and vote to affect the priority of the items