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 EventTarget defines a set of objects to serve as the target of an event result. Each target creates a
set. It would be good to be able to combine those with set operators (union, intersection, difference, and negation). This would require two things:
The obvious introduction of new AgentEventTarget types implementing those operators.
Upgrade of parsing in the EventSystem. Currently, the parsing assumes that all targets are immediate children of the <EventSystem> tag. The set operators will have nested target tags. The parsing needs to handle this and reconcile names.
More generally, the idea of defining a set of agents is more generally useful -- such as defining agent goals #142). The core functionality is the same -- given the world of agents, create a subset based on arbitrary criteria. That same functionality should be available to both events and other mechanisms without duplicating code. This more general idea probably requires its own issue.
The text was updated successfully, but these errors were encountered:
The
EventTarget
defines a set of objects to serve as the target of an event result. Each target creates aset. It would be good to be able to combine those with set operators (union, intersection, difference, and negation). This would require two things:
AgentEventTarget
types implementing those operators.EventSystem
. Currently, the parsing assumes that all targets are immediate children of the<EventSystem>
tag. The set operators will have nested target tags. The parsing needs to handle this and reconcile names.More generally, the idea of defining a set of agents is more generally useful -- such as defining agent goals #142). The core functionality is the same -- given the world of agents, create a subset based on arbitrary criteria. That same functionality should be available to both events and other mechanisms without duplicating code. This more general idea probably requires its own issue.
The text was updated successfully, but these errors were encountered: