Pixel Movement [The Order of Execution]

ID:863121
 
Jul 11 2012, 12:01 am (Edited on Jul 11 2012, 12:21 pm)
(See the best response by Zaoshi.)
I need a exact order of how Cross/Enter, Crossed/Entered, Uncross/Exit, Uncrossed/Exited

As to what I think the reference says, the correct order would(Logically) be
1.Cross
2.Crossed
and if the movement continues
3.Uncross
4.Uncrossed

But experimentally I have not found this true.
Code:
obj
 Cross(atom/movable/O)
  world<<"[O] tries to cross [src] -- ([world.time])"
 Crossed(atom/movable/O)
  world<<"[O] crossed [src] -- ([world.time])"
 Uncross(atom/movable/O)
  world<<"[O] tries to uncross [src] -- ([world.time])"
 Uncrossed(atom/movable/O)
  world<<"[O] uncrossed [src] -- ([world.time])"

Problem description:
Experimentally it goes like
1.Cross
2.Crossed
and if the movement continues
3.Uncrossed //?
4.Uncross

Compiling and running it gives the order as mentioned above..

I want to know whether 'that is how they are called' or because 'either of the operation is delayed/slept'!



Jul 12 2012, 4:51 am (Edited on Jul 13 2012, 2:58 am)
Here is a Project to demonstrate what I mean.
Jul 12 2012, 9:39 am
Best response
Project seems to have two Uncross. If you change second into Uncrossed then it all makes sense.

Edit:
I seem to receive two Cross calls, but everything else calls just once.
Jul 13 2012, 9:13 am
Thanks.. for pointing out my silliness.