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

Fix Issue #42 #59

Merged
merged 2 commits into from
Feb 22, 2019
Merged

Fix Issue #42 #59

merged 2 commits into from
Feb 22, 2019

Conversation

Miiite
Copy link
Contributor

@Miiite Miiite commented Feb 15, 2019

This PR has for goal to fix the issue #42

Having looked at this stackoverflow post it seems that setting .Enabled = false on a UIRefreshControl does not do anything, because it's actually the UIScrollView wrapping the UIRefreshControl that decides whether or not the control should be displayed.

Following that logic the solution seems to simply remove the UIRefreshControl from its Superview when the property IsPullToRefreshEnabled is set to false, and to try to insert it again when IsPullToRefreshEnabled is set to true.

Also updated the ListViewPage sample, to demonstrate the working databinding on the IsPullToRefreshEnabled property.

Also fixed a typo in ListViewPage.cs refreshView.SetBinding(PullToRefreshLayout.IsRefreshingProperty**, ,** new Binding("IsBusy", BindingMode.OneWay));
that was preventing the sample project from building.

Note: Changes to the .csproj file are automatically applied by Visual Studio for mac

@jamesmontemagno jamesmontemagno merged commit e691479 into jamesmontemagno:master Feb 22, 2019
@Miiite Miiite deleted the issue-42 branch February 22, 2019 08:24
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.

2 participants