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

Calculate container corners for validate candidates #25

Merged
merged 7 commits into from
Aug 14, 2023

Conversation

abbigrundy
Copy link
Contributor

Description

Consider the position of a valid container corners when calculating the best container move to.

Motivation and Context

When there are multiple small containers that overlap each other in rows, a container that was at the end of the row could skip the row above/below and have some unexpected behaviour moves.

For example pressing right at 22 would skip 15 and go to 8. Now with this fix, a right press from 22 goes to 15 as it now considers the corners of candidates. It considers the exit direction you are leaving a container, and if a candidates corners are within that side. So as 15's right corners are to the right of the leaving container (22) it is a valid candidate to move to.
Screenshot 2023-08-14 at 10 36 17

How Has This Been Tested?

Added a new test case and existing test pass.

Checklist:

  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@abbigrundy abbigrundy requested a review from a team as a code owner August 14, 2023 10:00
Copy link
Contributor

@Murreey Murreey left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@abbigrundy abbigrundy merged commit dfac028 into master Aug 14, 2023
1 check passed
@abbigrundy abbigrundy deleted the calculate-container-corners branch August 14, 2023 11:42
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