Hidden/lock objects by canvas

Hello,

I would like to suggest this feature:

<img src="https://dl.dropbox.com/u/47035927/temp/hidden%20and%20lock%20sprites%20on%20the%20scenario.png" border="0">https://dl.dropbox.com/u/47035927/temp/hidden%20and%20lock%20sprites%20on%20the%20scenario.png

And the scenario objects by canvas, where you'll can lock objects on the canvas, and hidden them to help you select and place other between two objects.

Why I'm suggesting this is because I never can select and move the objects between a scenario object (who need to be in the same layer of the other objects) and the behind small objects.

<img src="https://dl.dropbox.com/u/47035927/temp/canvas.png" border="0">

To move the player on the image above, you need to move the mountain to another layer, hide it and move the player =\</p>

Why not just organise your objects on to lots of separate layers? E.g. background, platforms, game objects, foreground, etc.

That's an organization type =]

This way will not impact on the game performance for large projects?

I'll try to organize like you said and see if works fine.

Thanks.

Edited: The use of many layers is absolutely viable and is very nice and clean =P

Amazing, I get stuck in my thoughts because of the use of old tools using different systems.

Recommended, and it's a best practice to be ADD on the construct.net/en article.

It's mentioned in Performance Tips:

b]Common misconceptions

...

Number of layers usually has no effect, unless most of the layers have changed their opacity or use 'force own texture'. However typically there is no performance impact from using multiple layers.

In other words, if you don't change any layer opacities or use 'force own textures', 100 layers each with a few objects is rendered as efficiently as having all the objects on 1 layer.

I would definitely suggest you start organizing with layers, because it can do exactly what you are asking.

If I didn't use layers I'd be having a whole load of hassle and pain. It's fundamental to the way I work.