You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe there is an issue with where the notify event happens when using AlsoNotifyFor.
Using the code:
[AlsoNotifyFor("CanEnterText")]
public ListCodeResultObject Selection
{
get { return selection; }
set
{
if (selection == value) return;
selection = value;
Dto.ServiceCommitmentText = selection.AdditionalInfo;
Dto.ServiceCommitmentTemplateId = selection.CodeId;
}
}
public bool CanEnterText { get { return Dto.ServiceCommitmentTemplateId != (int)SpecificCode.None; } }
causes the CanEnterText property to be ready by the UI before the DTO has been updated as opposed to when the entire setter has completed. The results being that the CanEnterText property shows what was previously chosen instead of the current selection. I would expect that AlsoNotifyFor should put all additional notify actions at the end of the property like NotifyPropertyWeaver did.
The text was updated successfully, but these errors were encountered:
I believe there is an issue with where the notify event happens when using AlsoNotifyFor.
Using the code:
causes the CanEnterText property to be ready by the UI before the DTO has been updated as opposed to when the entire setter has completed. The results being that the CanEnterText property shows what was previously chosen instead of the current selection. I would expect that AlsoNotifyFor should put all additional notify actions at the end of the property like NotifyPropertyWeaver did.
The text was updated successfully, but these errors were encountered: