My Testing department just caught this, but it might have been happening all along and nobody noticed. I have an UltraCombo control that I have bound on a WinForm. On my form, there are some cases where I set the combo's ReadOnly property to TRUE so that the user cannot change the value. However, if I just click on the combo, the text is immediately blanked out. I don't want to disable the control because I have buttons in the control that need to be enabled, so the ReadOnly property is my only choice.
I have put breakpoints into my code and the BeforeDropDown event is firing (not sure why the control should even allow that since the ReadOnly property is true). I even put code in this event to cancel, but the text is still wiped out. The AfterCloseUp event does NOT seem to fire, so I'm not sure what to do at this point.
I have installed all of the latest service packs for NetAdvantage WinForms.
Hi rehemann,
After initial investigation of this issue, I believe that it is possible that the ultraCombo’s value is being altered unintentionally, elsewhere in your project.
Given a scenario where you have a discrete UltraCombo control that is also read-only; the value and associated text will remain static during the course of normal user interaction. It is however certainly possible to alter the value and displayed text explicitly thru code even when the control is set to read-only.
After testing this scenario, I have been unsuccessful in reproducing the behavior that you have described; however, I would be more than happy to further investigate a sample project where this issue may be produced, in order to determine a solution.
If you have any further questions at all regarding this issue in the meantime or if you are able to provide the before mentioned sample, please let me know.
Sincerely,Chris KDeveloper Support EngineerInfragistics, Inc.www.infragistics.com/support
Hi,
I cannot think of any reason why simply clicking on the control should change the value, regardless of whether it's Read-Only or not.
My first guess would be that you are handling an event on the control, like the MouseDown, MouseUp, or Click event and something in your code is changing the value. If that's not the case, then I'm out of ideas.
What version of the controls are you using?
Can you duplicate this behavior in a small sample project?