I’m finding that something about the ImageOp caching in FreeRotator is messing things up when you have more than one FreeRotator trait. It seems to work okay if the second one allows arbitrary rotations, but not if the first one does.
- Give a piece two Can Rotate traits. Let the first first one allow arbitrary rotations, the second one not.
- Create a piece, arbitrary-rotate it to some angle, then cycle through the allowed angles of the other rotator trait
- Now arbitrary-rotate it to a new angle. When you cycle through the allowed angles now, some of them will be messed up.
Post generated using Mail2Forum (mail2forum.com)