You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug:
In the domain of floor tile naming, the tile names are in reverse order. Specifically, tile_0-1 represents the coordinate (1,0) in grid coordinates rather than (0,1). While this should not be an issue due to: (assign (?from y x) (function distribute_grid_around_point (objects ?from)))
which should place the tile in the correct position, changing the order of properties does not take effect. The properties are still updated as: (assign (?from x y) (function distribute_grid_around_point (objects ?from)))
Expected Behavior:
Given (assign (?from y x) (function distribute_grid_around_point (objects ?from)))
The second digit should represent the object's x position, and the first digit should represent the y position.
Observed Behavior:
The custom function parses the first digit as the x position and the second digit as the y position, regardless of the provided order.
The text was updated successfully, but these errors were encountered:
Describe the bug:
In the domain of floor tile naming, the tile names are in reverse order. Specifically, tile_0-1 represents the coordinate (1,0) in grid coordinates rather than (0,1). While this should not be an issue due to:
(assign (?from y x) (function distribute_grid_around_point (objects ?from)))
which should place the tile in the correct position, changing the order of properties does not take effect. The properties are still updated as:
(assign (?from x y) (function distribute_grid_around_point (objects ?from)))
Expected Behavior:
Given
(assign (?from y x) (function distribute_grid_around_point (objects ?from)))
The second digit should represent the object's x position, and the first digit should represent the y position.
Observed Behavior:
The custom function parses the first digit as the x position and the second digit as the y position, regardless of the provided order.
The text was updated successfully, but these errors were encountered: