Latest version: just clicking in the control or dropping down the combo fires the validated event. How am I supposed to validate edits without repeating the validations a million times? The ValueChanged event is useless since it changes on every key stoke and on a key/item population, returns the text as the value rather than the selected value (since no selected index).
What event if any is there to validate changes ONCE only when the change is completed and requires validation? The AfterEditExit and related events also seem to me useless as they fire even when no edits are made (even when control is readonly). What is the purpose of these events if they have nothing to do with an Edit?
Hi,
I just wanted to know if you were able to solve your issue based on my suggestions or you still need help? Just let me know.
Thank you.
I am seeing the same problem. On opening the form the ComboEditor (left control) has the focus. If I just first click in the second combo (ComboBox) the Validated event of the first combo fires even though no edit was made. If I just tab back and forth from control to control, the event fires on each, even though no edit is being made.
Hello,
I am just checking about the progress of this issue. Let me know If you need my further assistance on this matter?
Thank you for using Infragistics Components.
Ok, so the validating events occur regardless of whether any edits occurred. So these would seem to be useless events to validate edited data or take actions after validated edits, since they would occur every time fields were tabbed through, even in read only mode. What is a user supposed to do, write code to check on old values vs. new values everywhere before doing anything? What action would a user take in a Validating Event or Validated Event that did not have to do with an actual Edit?
How about your Before Edit and Before Enter Edit and After Edit events, etc. They fire even when readonly mode, so why are Edit's beginning and ending in readonly mode? Also, why would they fire when being tabbed through and no edit beginning (theoretically). Could you explain what these events are supposed to serve, unless again, a user is supposed to write code everywhere checking whether an actual Edit (data changed) actually occured in the field (I don't see and e.ActuallyEdited argument or similar)?
I am just checking about the progress of this issue. Let me know If you need any further assistance on this matter?
Hello ,
If you want to know if the user has changed the value of UltraComboEditor you should use some event which occurs after the value was changed like ValueChnaged event.
About the validating event its purpose is to check if the user was enters valid value for the component and if not you could display some error indication, for example you could use ErrorProvider, and also you could prevent customer to leave the component if the input value is not valid. Our components should be comply with Microsoft rules for firing of events, so when Microsoft changes the rule for firing of Validating event, then we will change it too.
Our BeforEnterEditMode, BeforeExitEditMode, AfterEnterEditMode and AfterExitEditMode are raised depends on the state of the editor (this doesn’t meant the they will occur if customer enters a value or not. This is like a door, those event are firing depend of the state of the door, if you will go through the door or not do not affect onto those events. For this there is an event ValueChanged.). More information about UltraComboEditor’s Members you could find on the following link.
http://help.infragistics.com/Help/NetAdvantage/WinForms/2011.1/CLR2.0/html/Infragistics2.Win.UltraWinEditors.v11.1~Infragistics.Win.UltraWinEditors.UltraComboEditor_members.html
Please let me know if you have any further questions regarding Infragistics Components.