Bug 311288 - Allow selections to properly represent multiple entities
Summary: Allow selections to properly represent multiple entities
Status: RESOLVED FIXED
Alias: None
Product: AMP (ARCHIVED)
Classification: Modeling
Component: AMF (show other bugs)
Version: 0.7.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: M2   Edit
Assignee: Miles Parker CLA
QA Contact: Miles Parker CLA
URL:
Whiteboard:
Keywords:
: 314989 (view as bug list)
Depends on:
Blocks: 311289
  Show dependency tree
 
Reported: 2010-05-01 16:15 EDT by Miles Parker CLA
Modified: 2010-05-30 14:45 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Miles Parker CLA 2010-05-01 16:15:01 EDT 
At this point, selections actually only contain the single best match for a given query, selected randomly of course. This works fine for movements and simple sets, but we want to support setting multiple values and calculating statistics on sets of selected agents. This will be late bound on code-generation so that we don't unnecessarily search for all agents when one would suffice. A selection of all agents will be defined by adding an "all" funciton Query Action to the selection. (This is one reason we changed the name of the "All Action".)
Comment 1 Miles Parker CLA 2010-05-29 19:29:57 EDT 
*** Bug 314989 has been marked as a duplicate of this bug. ***
Comment 2 Miles Parker CLA 2010-05-30 14:45:27 EDT 
This is implemented but not yet fully tested. It works only for Escape/Ascape target.