 
| Sender: |
|
| Date: |
Wed, 26 Feb 2014 20:36:53 -0500 |
| MIME-version: |
1.0 (Mac OS X Mail 7.2 \(1874\)) |
| Reply-To: |
|
| Content-type: |
text/plain; charset=iso-8859-1 |
| Subject: |
|
| From: |
|
| In-Reply-To: |
|
| Content-Transfer-Encoding: |
8bit |
| Parts/Attachments: |
|
|
On Feb 26, 2014, at 8:29 PM, Megan Olsen <[log in to unmask]> wrote:
> So is this true in all cases? Is there any way around that?
It's true in all cases. But the easy way around it is as follows:
1. Make TWO fields. Call them A and B. At start(), make them hold the same exact stuff.
2. Agents read field A to get their sensor information, but they make changes to field B.
3. A special agent, scheduled repeating, but at a later ordering (say ordering = 2), copies field B to field A, overwriting field A's contents.
Note that if your agents move around, they'll need to make sure that they don't overwrite each other in field B.
Sean
|
|
|
