Hi @all
we just installed release 14.1.20141.2059 of the Windows Forms controls and observed a problem, that was not present with Version 13.2.
If we set the same value for an UltraOptionSet twice, the value becomes null.
e.g. UltraOptionSet has initial value 0
UltraOptionSet.Value = 1; // Value becomes 1
UltraOptionSet.Value = 2; // Value becomes 2
UltraOptionSet.Value = 2; // Value becomes null
Is this a known issue?
Best regards,
Alex
Hello Alex,
Thank you for contacting Infragistics.
I created the attached sample to test the issue you described. It contains an UltraOptionSet with several items and a button. When the button is clicked, the UltraOptionSet.Value property is set to 2 and the value of the Value property is printed to Visual Studio's Output window. When I run the sample, 2 is printed to the Output window every time the button is clicked.
I'd like you to compare my sample with yours. If you're not able to determine why your sample is showing the behavior you described, please zip up your project and attach it to this thread.
Hello Dave,
thank you for four fast reply. Attached please find "my" example. Indeed it's yours. I only changed the DataType of the Items to 16 bit signed int (and not 32 bit) to produce the problem.
Best regards
Hi Alex,
Have you had a chance to test the latest service release, and has it resolved the issue for you? Please let me know.
Thank you for your response.
This issue has been resolved in the latest Service Releases as of the date of this post for Infragistics for Windows Forms 2013 Volume 2, 2014 Volume 1, and 2014 Volume 2. To download the service release, log in to ‘Account’ and select ‘Keys & Downloads’. Select the appropriate tab for this product; then the license key. The available service releases (Hot Fixes) should now be listed on the page.
Our documentation includes a Breaking Changes and Known Issues section.
Please let me know if I may be of further assistance.
thank you for your efforts!! I implemented a workaround which sets a new value only if it is different from the old one. Then it seems to work as desired. I will remove it after the bug is closed.
Do you have a link, where you list all known issues of the current version (not the Service Release Notes)? Then I could check if there are other problems we should be aware of.
Thank you very much.
Once I changed my sample to use 16-bit signed integers, I also reproduced the issue in the latest build of Infragistics 2014 Volume 1 as well as the latest build of Infragistics 2013 Volume 2. I did not reproduce the issue with the initial volume release of either volume.
I have reported this to our engineers and I have created support case CAS-142999-S5S3D8 to track this.