Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Renderable bounds do not respect anchor point #833
Comments
Closed
obiot
added a commit
that referenced
this issue
Dec 26, 2017
allows to properly takes in account anchor and transform for any me.Sprite object (including me.GUI), including proper detection of pointer Events. this is first partial implementation only for me.Sprite objects, as applying the same to the base me.Renderable class will trigger further breaking changes in me.Entity TODO : - me.Renderable class, including me.Entity - properly fix the debugPanel (Sprite BB drawing is off for now)
|
partially done at me.Sprite level |
adrianhartanto0
pushed a commit
to adrianhartanto0/melonJS
that referenced
this issue
Feb 19, 2018
…ite Bounding Rect allows to properly takes in account anchor and transform for any me.Sprite object (including me.GUI), including proper detection of pointer Events. this is first partial implementation only for me.Sprite objects, as applying the same to the base me.Renderable class will trigger further breaking changes in me.Entity TODO : - me.Renderable class, including me.Entity - properly fix the debugPanel (Sprite BB drawing is off for now)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
When trying to get the bounding rect of a renderable through getBounds() (or just using .left etc.), the anchor point is totally ignored. This results in bounding box being offset in relation to what is actually drawn.