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
{{ message }}
This repository has been archived by the owner on Apr 18, 2022. It is now read-only.
With PR #67, there is no way to access the world, which would have made it possible to add resources, Systems and the native functions of a World. This needs to be fixed in some way.
Currently, Broadcaster only provides some sugar for World.
The text was updated successfully, but these errors were encountered:
Emilgardis
added a commit
to Emilgardis/amethyst
that referenced
this issue
Jul 19, 2016
Exposing it makes it possible to add Systems, known as Processors in
`amethyst::ecs`. This also exposes every native function.
A problem with this approach is that it is not optimal, simply using World
instead of Broadcast in `Context` is also not optimal. See amethyst#67 and amethyst#74.
It would still be impossible to add Systems because it would require a Planner that needs to own the World, so it won't be possible to move the World from Broadcaster while calling Planner::new(). And I am not sure if there are use cases for exposing resource creation, access functionality.
I also think that it would make sense to keep entities in Broadcaster read only, since they represent events and it adds the guarantee that the event you publish will be the same event when it is polled.
With PR #67, there is no way to access the world, which would have made it possible to add resources,
Systems
and the native functions of aWorld
. This needs to be fixed in some way.Currently,
Broadcaster
only provides some sugar forWorld
.The text was updated successfully, but these errors were encountered: