Official_GameTeam wrote:

I am now realising that an empty “dummy” layer may be a bad idea… what is happening if you move a sprite to an emptied layer? does it create an other empty where it was? or is there now one less layer? how are clones working? do they automatically fill empty layer?

I may remove this part of a suggestion soon. what are you thoughts?

Official_GameTeam wrote:

the way that “layers” are currently function is simple: each sprite and clone is having a different layer number. this number is controls if the sprite is seen “above” or “below” another sprite. you can be moving sprites up and down by layers, and they do displace other sprite when this is done. however, in a project with a many sprite, or many clone, it is not always not entirely not easy to know where is a layer-sprite. to fix this … ..

I think that it will be a good idea to be have a layer hierarchy, like the one for “costumes”. this will make it easy er to see and re arrange sprites on the layers. another feature that can be add with this, is the ability to make an empty “dummy” layer, with no sprite in it. this way a layer can be “reserved” for later.

finally, this 3rd suggestion only make sense if BOTH of the above are add to scratch: a new block:

go to layer () if that layer is empty :: looks

(this is also a cool: thank Quantum-Cat for a concept)

<layer () is empty? :: looks>

(layer number)

musicROCKS013 wrote:

Official_GameTeam wrote:

I am now realising that an empty “dummy” layer may be a bad idea… what is happening if you move a sprite to an emptied layer? does it create an other empty where it was? or is there now one less layer? how are clones working? do they automatically fill empty layer?

I may remove this part of a suggestion soon. what are you thoughts?

I think that empty layers would be confusing and hard to manage, so either find a sure, clear way to how they work, or remove that part entirely.

m4th154w350m3 wrote:

Official_GameTeam wrote:

the way that “layers” are currently function is simple: each sprite and clone is having a different layer number. this number is controls if the sprite is seen “above” or “below” another sprite. you can be moving sprites up and down by layers, and they do displace other sprite when this is done. however, in a project with a many sprite, or many clone, it is not always not entirely not easy to know where is a layer-sprite. to fix this … ..

I think that it will be a good idea to be have a layer hierarchy, like the one for “costumes”. this will make it easy er to see and re arrange sprites on the layers. another feature that can be add with this, is the ability to make an empty “dummy” layer, with no sprite in it. this way a layer can be “reserved” for later.

finally, this 3rd suggestion only make sense if BOTH of the above are add to scratch: a new block:

go to layer () if that layer is empty :: looks

(this is also a cool: thank Quantum-Cat for a concept)

<layer () is empty? :: looks>

or even better

(layer number)

Official_GameTeam wrote:

m4th154w350m3 wrote:

Official_GameTeam wrote:

the way that “layers” are currently function is simple: each sprite and clone is having a different layer number. this number is controls if the sprite is seen “above” or “below” another sprite. you can be moving sprites up and down by layers, and they do displace other sprite when this is done. however, in a project with a many sprite, or many clone, it is not always not entirely not easy to know where is a layer-sprite. to fix this … ..

I think that it will be a good idea to be have a layer hierarchy, like the one for “costumes”. this will make it easy er to see and re arrange sprites on the layers. another feature that can be add with this, is the ability to make an empty “dummy” layer, with no sprite in it. this way a layer can be “reserved” for later.

finally, this 3rd suggestion only make sense if BOTH of the above are add to scratch: a new block:

go to layer () if that layer is empty :: looks

(this is also a cool: thank Quantum-Cat for a concept)

<layer () is empty? :: looks>

or even better

(layer number)

yes, it's in the post now : )

ChooChoo62 wrote:

Why not just add the list as a tab in the Editor, and list layers as you would the costumes in a sprite; where they can be rearranged vertically to suit needs. That would make not just understanding layers themselves easier, but if a sprite wasn't on the correct layer, you could just drag it in the Layer tab, instead of having to fiddle with the layer blocks.

([layer number v] of [sprite v])
(layer number ::looks)
(layer number of clone () of [this sprite v] ::looks)
(layer number of clone () of [sprite v] ::looks)
<layer () empty? ::looks>
go to layer () ::looks

if <layer () empty? ::looks> then
go to layer () ::looks
end

medians wrote:

Alright, bringing this up.

medians wrote:

medians wrote:

Alright, bringing this up.