So basically, in MMF, if you want an object to stay on some other object that moves with the basic movements, you can just put
Always: set XY position of the first object to XY of the second.
So the first object stays on the moving object. In MMF 2, this should work perfectly and there shouldn't be any 'lag' between the moving and the non-moving object.
Other thing is when the moving object moves with values, like always set X to X + value A. Then the object that should be on the moving object comes a bit after the moving object. This can however be fixed with
Always: set X of object 1 to X of object 2 + value A of object 2
And after that there's, again, no lag and it works perfectly.
However (sorry for the long introduction), I've been trying to do an object with a transparent area in the middle, that would get the RGB colour in that transparent area. I've been using LIJI's Pixel Object, that can get the RGB value of a single pixel. Iv'e set it so that the Pixel object always gets the RGB in the hot spot of the object (and the hot spot is in this transparent area). When the object wasn't moving, it worked perfectly, it got the colour behind the object. But, the problems began when the object started moving. Seems like the Pixel object lags a bit too much, so even with that 'set X = X + value A' -method I described up there, it doesn't get the correct pixel, but some (actually quite many) pixels 'after' the moving object. This makes it impossible for me to create the idea I had in my mind which is quite sad. 
But hey, would you have any alternate extensions for this, or some help on how to fix this? The game this thing should be on is scrolling, so I don't think if overlay would work... Anyway, I thank everyone who can give any advice. 
Sorry again for the long post, I hope it's not too confusing.
