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
When Phaser.Gameobjects.Image from an atlas made by TexturePacker is added to scene, and the Frame of such image has a custom Pivot Point, this image in Phaser will automatically have it's pivot point set to the pivot point set inside the TexturePacker IDE.
Is same possible to be done, when NineSlice is used for such atlas Frame? Currently the NineSlice created using frame with custom Pivot point will not inherit this custom pivot point. This introduces a discrepancy, when Image or NineSlice is used for same Frame.
The image above, when NineSlice is used to display it, will not take it's custom pivot point into account, but will have its origin set to (0.5,0.5)
EDIT: it seems NineSlice doesnt support setOrigin at all. Can it be made to support custom origin?
The text was updated successfully, but these errors were encountered:
Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.
When
Phaser.Gameobjects.Image
from an atlas made by TexturePacker is added to scene, and the Frame of such image has a custom Pivot Point, this image in Phaser will automatically have it's pivot point set to the pivot point set inside the TexturePacker IDE.Is same possible to be done, when NineSlice is used for such atlas Frame? Currently the NineSlice created using frame with custom Pivot point will not inherit this custom pivot point. This introduces a discrepancy, when Image or NineSlice is used for same Frame.
The image above, when NineSlice is used to display it, will not take it's custom pivot point into account, but will have its origin set to (0.5,0.5)
EDIT: it seems NineSlice doesnt support
setOrigin
at all. Can it be made to support custom origin?The text was updated successfully, but these errors were encountered: