This is a migrated thread and some comments may be shown as answers.

NumerocUpDown with UpdateSourceTrigger and UpdateValueEvent

3 Answers 41 Views
NumericUpDown
This is a migrated thread and some comments may be shown as answers.
Pierre
Top achievements
Rank 1
Pierre asked on 21 Jan 2016, 11:00 AM

Hello,

I just ported my solution from .NET 3.5 to .NET 4.6.1 and updated Telerik from version 2012.2.912.35 to 2015.3.1104.5.

This code used to work fine, the setter of the property was called when the control lost focus:

 <telerik:RadNumericUpDown Value="{Binding UIExceeding, Mode=TwoWay}" SmallChange="0" LargeChange="0">

 

After the framework and Telerik was updated, the setter was never called anymore. To go back to how it used to work, I had to add UpdateSourceTrigger=LostFocus and UpdateValueEvent="PropertyChanged":

  <telerik:RadNumericUpDown Value="{Binding UIExceeding, Mode=TwoWay, UpdateSourceTrigger=LostFocus}" SmallChange="0" LargeChange="0" UpdateValueEvent="PropertyChanged">

 

Could you tell me what changed in between versions?

Thanks in advance

 

 

3 Answers, 1 is accepted

Sort by
0
Nasko
Telerik team
answered on 25 Jan 2016, 12:16 PM
Hello Pierre,

The observed by you behavior is not an expected one. Your initial code should be working as expected with version 2015.3.1104.5 - as soon as the focus is moved out of RadNumericUpDown the setter should be called as expected. Please, check the attached video and let us know if we missed something.

It will be great if you are able to send us a sample that demonstrates the behavior observed on your side - thus we could be able to investigate it further.

Hope this helps.

Regards,
Nasko
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
0
Pierre
Top achievements
Rank 1
answered on 25 Jan 2016, 12:52 PM

Hi,

Thanks for you answer. Your video seems indeed to demonstrate that there's no problem regarding the Telerik component (which is fortunate!).

I tried to remove all optional attributes (Style, Converter, etc.) in order to see if they were causing this behaviour somehow, but no change, still no call to the setter when the focus is lost...

My radNumericUpDown is embedded in a bunch of other controls though (it's in the <DataTemplate> of a <DataGridTemplateColumn.CellTemplate>), so the root cause is probably located in those parent controls' configurations.

I'll keep looking for the cause and try to isolate a stand-alone sample that reproduces the issue to post here.

Thanks for your investigation

0
Nasko
Telerik team
answered on 25 Jan 2016, 01:12 PM
Hi Pierre,

As soon as you are able to isolate the issue or have some additional information that might help us to reproduce it on our side, please contact us.

Meanwhile, if you have any additional questions or concerns regarding Telerik controls, please do not hesitate to contact us.

Regards,
Nasko
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
Tags
NumericUpDown
Asked by
Pierre
Top achievements
Rank 1
Answers by
Nasko
Telerik team
Pierre
Top achievements
Rank 1
Share this question
or