Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with AlsoNotifyFor #52

Closed
CKozanecki opened this issue Mar 11, 2013 · 1 comment
Closed

Issue with AlsoNotifyFor #52

CKozanecki opened this issue Mar 11, 2013 · 1 comment

Comments

@CKozanecki
Copy link

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.

@SimonCropp
Copy link
Member

this is the wrong place for this issue. please re-raise it here https://github.com/Fody/PropertyChanged/issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants