I see... that is why the name of the array is changingArrayOfXYZLocations. :p
Have you tried what Jerome said, or what Kevin did ? On Wed, Nov 3, 2010 at 6:40 PM, Nick <[email protected]> wrote: > Thanks for your response Aji! > > Let me say it again and try to be clearer about this. > > The array 'changingArrayOfXYZLocations' does change. > > When the user clicks, changingArrayOfXYZLocations is given a set of x, > y, z points for all of the assets. The assets move closer and closer > to this position (1) and then stop. That's what they're supposed to > do. > > Then when the user clicks on something else, > changingArrayOfXYZLocations changes to a new array of x, y, z > locations for all of the assets. Now we start the process all over > again moving all of the assets closer and closer until they get to > their new position (2). > > The issue is that if and when they do get to position 1, the get stuck > and won't then move to position 2. If they don't get to position 1 by > the time the user changes to position 2, they will then accept this > new position and move to it. > > So what happens is that when I send the assets to position 1, they all > start on their way. Some make it and stop and some take longer and > before they get there, I send the assets to position 2. The ones that > did make it to position 1 stay there and the ones that didn't yet make > it move to the new postion. ALL of them should be moving to the new > position. > > This all traces out fine. I can see the values changing for all of the > assets. But visually they are not moving on screen. And I can see from > the traces that it's when the asset reaches it's position is when it > gets stuck. > > The assets themselves don't ever change the arrays that feed > changingArrayOfXYZLocations. changingArrayOfXYZLocations is a pointer > to 4 other arrays of data. And those 4 arrays are fixed. I never alter > them. > > Thanks, Nick > > > > -- Aji Pamungkas
