Translate pointer event coordinates to screen coordinates.

[guillerodriguez]

This fixes the case for layers that have transforms applied
(for example, rotations of 90, 180, 270 degrees)

[samskivert]

This seems weird. Pointer event coordinates are in screen coordinates, and in any case screen coordinates are presumably not what you want here because those reflect the physical orientation of the device, not your pseudo-rotated version.

It may be that the math is accidentally working out, but I think a more correct solution might be to have XYFlicker use the event.local coordinate which are the coordinates of the event translated into the coordinate space of the hit layer (which will account for whatever top-level rotation you have applied).

Can you try just changing:

        dest.set(-event.x(), -event.y());

to

        dest.set(-event.local.x, -event.local.y);

To see if that also fixes the problem? Because I think it should, and it makes more sense as the correct thing to do.

[guillerodriguez]

You are of course right. The math was working out because "translating the event to screen coordinates" was introducing a 90 deg rotation which "fixed" the behaviour in my use case. Should be fixed now.

(There's no event.local though, I assume you meant Interaction.local instead)