Skip to content

Unity 6.6 support - fix SetLayoutInputForAxis argument order - #537

Open
RunoLight wants to merge 1 commit into
Unity-UI-Extensions:developmentfrom
RunoLight:unity-6.6-api
Open

RunoLight wants to merge 1 commit into
Unity-UI-Extensions:developmentfrom
RunoLight:unity-6.6-api

Conversation

@RunoLight

Copy link
Copy Markdown

Unity UI Extensions - Pull Request

Replaces #536. That PR was opened against release and, after it was retargeted to development, could not merge: the branch also carried release-only commits (README, workflows, version bump) and conflicted with development.

This branch is development plus the Unity 6.6 layout fix only.

Overview

LayoutGroup.SetLayoutInputForAxis on Unity 6.6+ is (totalMin, totalMax, totalPreferred, totalFlexible, axis). The calls added in #530 appended an extra argument, so preferred, flexible, and axis were shifted. FlowLayoutGroup and TableLayoutGroup now pass totalMax in the second slot and keep the previous preferred and flexible values.

The other Unity 6.5 / 6.6 updates from #536 (GetEntityId, maxWidth / maxHeight, useLegacyMeshGeneration) are already on development.

Changes

Breaking Changes

  • No breaking changes. Older Unity versions keep the previous API through conditional compilation.

Related Submodule Changes

  • N/A

Testing status

  • No tests have been added.

Manual testing status

  • Argument order checked against the Unity 6.6 SetLayoutInputForAxis(totalMin, totalMax, totalPreferred, totalFlexible, axis) signature.
  • Compared with the calls already on development from Upversion development to 3.0.1-pre.1 [skip ci] #530, which appended a trailing argument and shifted preferred, flexible, and axis.

with conditional compilation to preserve back compability.
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.

1 participant