Skip to content

Conversation

@xied75
Copy link
Contributor

@xied75 xied75 commented Mar 24, 2017

Not sure if this is the supposed proper fix, but I've tried in my app and it works fine.

Without the UpdateLayout(); it only works randomly, I guess it takes time for the UI to refresh before we can scroll?

@dnfclas
Copy link

dnfclas commented Mar 24, 2017

@xied75,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@deltakosh
Copy link
Contributor

@Odonno and @skendrot : do you mind reviewing this one?

@xied75
Copy link
Contributor Author

xied75 commented Mar 28, 2017

@deltakosh Looks like everybody is pretty busy, may I take the courage to suggest merge this? For two lines of code it won't trigger the Big Red Button if something goes wrong. :) -- that is my naïve thinking, at least I should spot the bug first, or my app user...

}
}
}
else if (e.CollectionChange == CollectionChange.ItemInserted)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not also on deleted?

@xied75
Copy link
Contributor Author

xied75 commented Mar 28, 2017

When I try removing an item, it handled itself correctly. I thought adding code should be as small effect as possible.

@deltakosh
Copy link
Contributor

ok so it makes sense I wanted to be sure :)

@deltakosh deltakosh merged commit e635245 into CommunityToolkit:dev Mar 28, 2017
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

Successfully merging this pull request may close these issues.

3 participants