Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

[CollectionView] UWP- Updating the ItemsLayout type should refresh the layout #10316

Closed
wants to merge 11 commits into from
Closed

Conversation

EmilAlipiev
Copy link
Contributor

This is an update to this issue. It was closed with fix for Android and IOS but UWP wasnt working.
I have tried my best to fix the issue. I am not sure if that is the best way of fixing this. But it works fine. I didnt create a new test case because existing case 5354 can be used and it works fine like that.

Emil Alipiev and others added 5 commits February 9, 2019 04:47
…onInfo.DeviceFamily

UWP-Xbox sets TV...Surface tablets sets Desktop intead of Phone
Default was changed to be Unsupported Idiom

Co-Authored-By: EmilAlipiev <[email protected]>
upda from origin master
@EmilAlipiev EmilAlipiev changed the title [CollectionView] Updating the ItemsLayout type should refresh the layout [CollectionView] UWP- Updating the ItemsLayout type should refresh the layout Apr 13, 2020
@EmilAlipiev
Copy link
Contributor Author

can we get this fix? if anyone can review and accept it? it is so important for uwp :)

@EmilAlipiev
Copy link
Contributor Author

Can we get this fix merged please? This bug makes collectionview not usable for uwp.

Copy link
Contributor

@jsuarezruiz jsuarezruiz left a comment

Choose a reason for hiding this comment

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

Thanks for the PR @EmilAlipiev.

I've done some tests. The ItemsLayout change works (see other comments) but we also need a small change in ItemContentControl to force a Measure of the content.

uwp-items-layout-issue

@@ -186,6 +186,25 @@ protected override void HandleLayoutPropertyChanged(PropertyChangedEventArgs pro
break;
}
}
else if (property.Is(StructuredItemsView.ItemsLayoutProperty))
Copy link
Contributor

Choose a reason for hiding this comment

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

Changing the ItemsLayout used, switch between FormsListView and FormsGridView with the appropriate container in ItemsViewRenderer.cs, this block is not necessary.

@jsuarezruiz
Copy link
Contributor

To fix #10482 I created this related PR #10797. The issue is the same. So, take a look to this PR. After updating this PR we can link the issue and close the other PR. Let me know if you need help with something.

@EmilAlipiev
Copy link
Contributor Author

Hi @jsuarezruiz thanks for your reply. I have just checked your PR. it looks a bit different than mine. If you think that your one resolves the issue better i dont mind, please go ahead. I was just trying my best since nobody picked up this issue almost a year :) For me the most important thing is that we can use collectionview on uwp ;)

@jsuarezruiz
Copy link
Contributor

@EmilAlipiev I understand it and I really appreciate the effort, thanks!. We want the same, allow you use CollectionView in UWP without problems. If you complete the PR, I will be happy to review/help with it, etc.

@EmilAlipiev
Copy link
Contributor Author

@jsuarezruiz ok i applied your changes and pushed. please go ahead :) i hope to see this fix merged soon.

@samhouts samhouts self-requested a review May 28, 2020 00:52
@jsuarezruiz
Copy link
Contributor

Thanks for the changes. I have done tests and the behavior is now correct.

82464837-d1a5f700-9abe-11ea-9e19-7a4f96b3836e

@samhouts should we change the target to 4.7?. On the other hand, we could close #10797 or merge it too since it adds a specific sample to Core Gallery, etc.

@samhouts samhouts removed their request for review June 2, 2020 23:58
@samhouts samhouts requested a review from hartez June 2, 2020 23:58
@samhouts samhouts assigned hartez and unassigned samhouts Jun 2, 2020
@EmilAlipiev
Copy link
Contributor Author

@jsuarezruiz what is that conflict now? Do you have any idea how we can resolve it?

@rmarinho
Copy link
Member

rmarinho commented Jun 4, 2020

Hi @EmilAlipiev i fixed the conflict but seems the branch is not correct, there are changes to files that are not needed. Like FormsProgressBar.

Maybe is better to branch master, cherry-pick the commits you want and force push this branch again

@EmilAlipiev
Copy link
Contributor Author

Hi @rmarinho yes, i made a mistake yesterday and worked on another issue without creating a new branch. i have recognized after i pushed them. i need to separate them to a new branch. It is the confusion of working in a fork branch :)

@rmarinho
Copy link
Member

rmarinho commented Jun 16, 2020

@EmilAlipiev please open a new pr when ready.

Thanks

@rmarinho rmarinho closed this Jun 16, 2020
@EmilAlipiev
Copy link
Contributor Author

@rmarinho Should I open another PR for ProgressRing changes do you mean? I am bit confused here because when I look at the origin/master history, it shows my commit was merged. Is there something I am missing here?

image

@rmarinho
Copy link
Member

@EmilAlipiev this PR shows changes to the ProgressRing , but the title refers to ItemsLayout and CollectionView.

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

Successfully merging this pull request may close these issues.

5 participants