10-04-2021, 08:17 AM
Hi,
I looked quickly and I can see one problem in the code of the action to move a full stack of pieces about keeping the same state/rotation/value for each piece at each level, that's now fixed in our code and will be available in the next release.
However, I see that when you move a "king" piece to an empty site, you are going to add a piece on top of it with a local state of 0. Consequently, the top piece is not a king and move like a normal piece (same for the GUI, you do not see a red circle around it because the graphics metadata you are using is drawing a red circle only if the top piece has a state of 1, but if you comment the line (stackType Count), you will be able to see that the piece under this new piece has still the local state at 1 (in the new code)). So you will probably want to fix that on your description.
Regards,
Eric
I looked quickly and I can see one problem in the code of the action to move a full stack of pieces about keeping the same state/rotation/value for each piece at each level, that's now fixed in our code and will be available in the next release.
However, I see that when you move a "king" piece to an empty site, you are going to add a piece on top of it with a local state of 0. Consequently, the top piece is not a king and move like a normal piece (same for the GUI, you do not see a red circle around it because the graphics metadata you are using is drawing a red circle only if the top piece has a state of 1, but if you comment the line (stackType Count), you will be able to see that the piece under this new piece has still the local state at 1 (in the new code)). So you will probably want to fix that on your description.
Regards,
Eric