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
The current EntityRecord type only exposes the methods that would make change to the entity. This results in a situation where I have to keep both the Entity instance and the EntityRecord instance and have to distinguish them very carefully to call the getters of the former and the setters of the latter. This is very annoying.
If the EntityRecord type can expose all the Entity's getters, then I only need to have one EntityRecord instance to access all of an entity's information. This would also make sure that I wouldn't accidentally call the setters on the Entity instance, which would cause operations to be performed immediately. The same is true for the WorldRecord type.
Based on the full-functional EntityRecord type, systems that force the use of EntityCommandRecorder can also be implemented. For example, a ABufferedEntitySetSystem could offer an virtual method that looks like:
The current
EntityRecord
type only exposes the methods that would make change to the entity. This results in a situation where I have to keep both theEntity
instance and theEntityRecord
instance and have to distinguish them very carefully to call the getters of the former and the setters of the latter. This is very annoying.If the
EntityRecord
type can expose all theEntity
's getters, then I only need to have oneEntityRecord
instance to access all of an entity's information. This would also make sure that I wouldn't accidentally call the setters on theEntity
instance, which would cause operations to be performed immediately. The same is true for theWorldRecord
type.Based on the full-functional
EntityRecord
type, systems that force the use ofEntityCommandRecorder
can also be implemented. For example, aABufferedEntitySetSystem
could offer an virtual method that looks like:to make sure that all of its implementations would access the entity through a recorder and all operations would be cached.
The text was updated successfully, but these errors were encountered: