The most frustrating thing ever in scratch has to be controlling the layers that the sprites are on. A lot of the time go to front then go back (whatever amount) layers works but at other times it doesn't. Also right clicking a sprite and pressing "show" seems to mess up the layers.
I have spent an hour just trying to get the layers worked out on one project.
Offline
Very true. I'm getting tired of:
forever
go to front
go back # layers
end forever
Offline
keroro645 wrote:
Does it ell you where what layer a sprites on?
No it doesn't
Offline
hey archmage, i made a project for 1.4 bricks, take a look
Offline
Layers will be useful... But it will be cool if we receive only <Go above (Sprite)> and <Go below(Sprite)> blocks. When used in Java these methods done it perfectly
Offline
You're right.
On most projects using lots of layers (my racing game for example) i let them initialize automatically. Just add
broadcast [initialize] and wait
broadcast [start]
An "initialize" script should look like this:
Sprite1:
When I receive [initialize]
wait (0) secs
go to front
Sprite2:
When I receive [initialize]
wait (0.1) secs
go to front
Sprite3:
When I receive [initialize]
wait (0.2) secs
go to front
Sprite 1 will behind sprite 2 & 3
Sprite 2 will be in front of 1, behind 2
Sprite 3 will be on top of it.
Especially when I mess up the layers in development mode I am happy I added this
Click the green flag and everything's fine again...
I never use the go back to layer block, each sprite is on it's own layer which means they are actually sorted. (You pick out the one on top, ...) Depending on how fast the block execute, the layers are different each time.
Offline