Update relative coords of pieces so that algorithm works with one field #1

New Issue

felixm · 2023-10-16T20:49:16+02:00

felixm commented

2023-10-16 20:49:16 +02:00

The offset of some pieces are so, that iterating over the fields in order does not work.

We use this line to work around that:

for empty_coord in &field.empty_coords.as_slice()[0..2] {

Note that it takes two coords. This should not be necessary if the offsets are correct.

The offset of some pieces are so, that iterating over the fields in order does not work. We use this line to work around that: for empty_coord in &field.empty_coords.as_slice()[0..2] { Note that it takes two coords. This should not be necessary if the offsets are correct.

felixm referenced this issue from a commit

2023-10-19 14:03:24 +02:00

Orient all pieces rotations to 0 0 to resolve #1 and clean up.

felixm closed this issue

2023-10-19 14:03:24 +02:00

Sign in to join this conversation.

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: felixm/talos_solver#1