I am trying to make the paying pieces in one of my modules more interactive and as such I placed some “action buttons” on the basic pieces (through prototypes) to trigger some effects (morale, step losses, etc.)
Everything is working fine except one annoying thing that might make the whole idea moot:
when one rotates the basic piece (the game requires orientation within hexes), the action button mappings do not rotate with it so it becomes almost impossible to figure out where the button area was since the picture does not match the button position anymore.
Is there a way to prevent that behavior?
Note that the “rotation property” is listed below (in the basic piece window) the “prototype property” containing the layers/buttons etc. so the graphical layers rotate fine.
If I put the rotation property above the rest then none of my layers, including the action buttons, rotate (except for the basic piece which is below the rotation property).
Infortunately, Action buttons know nothing about rotation.
*********** REPLY SEPARATOR ***********
On 6/11/2011 at 12:17 PM freddel wrote:
If I put the rotation property above the rest then none of my layers,
including the action buttons, rotate (except for the basic piece which
is below the rotation property).
Infortunately, Action buttons know nothing about rotation.
*********** REPLY SEPARATOR ***********
On 6/11/2011 at 12:17 PM freddel wrote:
If I put the rotation property above the rest then none of my layers,
including the action buttons, rotate (except for the basic piece which
is below the rotation property).
It’s an interesting, non-trivial problem. You will need to scan the traits above the Action Button in the stack, totalling the degrees of rotation of any active FreeRotators and then apply an appropriate AffineTransformation to the Click Point before checking if the Button has been clicked.
It’s an interesting, non-trivial problem. You will need to scan the traits
above the Action Button in the stack, totalling the degrees of rotation of
any active FreeRotators and then apply an appropriate AffineTransformation
to the Click Point before checking if the Button has been clicked.
