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

Paged list layouts now support using bounds, instead of itemInsets #493

Merged
merged 2 commits into from
Jun 16, 2023

Conversation

kyleve
Copy link
Collaborator

@kyleve kyleve commented Jun 13, 2023

This updates Paged List Layouts to respect and use the bounds property, which will allow us to properly apply market screen widths in Market. I've removed itemInsets, since bounds.padding does this instead.

Checklist

Please do the following before merging:

  • Ensure any public-facing changes are reflected in the changelog. Include them in the Main section.

@kyleve kyleve force-pushed the kve/respect-layout-bounds branch from fc7020c to d17ebc0 Compare June 13, 2023 18:32
@kyleve kyleve requested a review from a team June 13, 2023 21:27
defaultWidth: bounds.width.clamp(pageSize.width)
)

var lastMaxY : CGFloat = 0
Copy link
Member

Choose a reason for hiding this comment

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

Looks like this was pre-existing but the name lastMaxY is a bit confusing for the horizontal direction.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I use width/height and x/y throughout these layouts, and then flip them based on direction; since I found it clearer than "axis/cross axis", which is what blueprint uses.

@kyleve kyleve enabled auto-merge June 15, 2023 23:37
@kyleve kyleve force-pushed the kve/respect-layout-bounds branch from 47c2327 to e32cf29 Compare June 15, 2023 23:40
@kyleve kyleve merged commit b84a964 into main Jun 16, 2023
@kyleve kyleve deleted the kve/respect-layout-bounds branch June 16, 2023 00:02
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