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 attempting to clean the me.Renderable implementation, and removing the unnecessary bounds objets, this caused a lots of problems, because of the type mismatch.
Also, it might not be fully used (e.g. in the collision detection), and there will be still a mismatch as Renderables use a me.ObscervableVector3d object type, but all shapes should at least uses a me.Vector3d type for the position object.
Anyway clean way maybe to mutate a me.Vector3d object to a me.ObscervableVector3d one (using Object.assign?)
The text was updated successfully, but these errors were encountered:
another solution to this, that we discussed in the past as well, would be to reimplement me.Rect as a pure "box" object, that would then only be used for bounding box, and would be the base class for renderable (since ultimately, we also want to replace the child bounds, and use the renderable bounds as bounding box).
which would then give the following :
Object pos type :
Object
pos
type :me.Vector2d
me.Vector2d
me.Vector2d
me.Vector2d
me.ObscervableVector3d
Inheritance Chain :
When attempting to clean the me.Renderable implementation, and removing the unnecessary bounds objets, this caused a lots of problems, because of the type mismatch.
Also, it might not be fully used (e.g. in the collision detection), and there will be still a mismatch as Renderables use a
me.ObscervableVector3d
object type, but all shapes should at least uses ame.Vector3d
type for the position object.Anyway clean way maybe to mutate a
me.Vector3d
object to ame.ObscervableVector3d
one (using Object.assign?)The text was updated successfully, but these errors were encountered: