Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
ISupportsInitializeNotification
interface in base control. While control is being initialized, no changes (being triggered by the control being populated) trigger a call toSave
and so do not appear in the undo historyInitializing
field was already added to reduce flicker on theconditionControl
, so moved this to use theISupportsInitializeNotification
mechanism for consistencyBeginInit
/EndInit
to batch multiple changes being made by selecting a relationship so this appears only onceSaveEventArgs
to indicate if change is being triggered by a keypress event or not. Keypress-generated events are ignored from undo historySave
event is still triggered on each keypress to update the rest of the UI but adds an extra event handler toValidated
event to trigger an extraSave
call when the user finishes editing the field so it can be added to undo history.