Tiled: Ability to lock layers

[xerosugar]

I think this should be added to prevent the user from working on the wrong layer.

[kheftel-old]

+1 for this

[bjorn]

Currently, hiding a layer can effectively be used to avoid working on a layer since this also disables the tools from working on the layer.

[xerosugar]

yes, but I still think that being able to see what is on the other layers (the locked ones) while you work on a new one would be nice.

[kheftel-old]

Agree with xerosugar

[alwex]

+1 also

[ncareau]

+1, currently our game has multiple layer and i throw an error when wrong tile are inserted into the special layer. Being able to lock the layer would be nice to prevent any unwanted tile inserted in that layer.

[superqix]

I don't usually +1 something, but now that we have scaleable objects, this feature is getting more important. We use lots of gradients on the topmost and bottommost layers that make it hard to nudge other objects in a map.

[bjorn]

Alright, I've added it to the roadmap. You can vote on it there. I'm still trying to find out how to prioritize features against each other. I definitely agree this would be a good to have feature, no question about it.

Sometimes I tell people they can support me on Patreon to help me get around to more features sooner, but I see you already are @superqix, so thanks a lot for your support! And to @kheftel as well of course!

[superqix]

Thanks for adding to the roadmap. I've been super impressed with updates since you went with Patreon funding, so keep up the good work.

I'm working toward releasing a new Lua loader for CoronaSDK/Love2D so hopefully that will open you up to a new group of Patreons.

[kheftel-old]

It's been awesome to see the pace of updates increase as patreon funding grows :). This is a great piece of software, and @bjorn you have done excellent work with it!

[bjorn]

That's great to hear, thanks!

As for growing the funding, this seems really hard from the current level. The pace rather stopped once the first goal was reached, but I'd still like to reach the second goal as well. I've opened up issue #1064 for this. :-)

[EdenIndustries]

I've actually already implemented layer locking in our local version of Tiled. Do you want me to try a pull request for it? Or did you have a plan in mind for it already?

[bjorn]

@EdenIndustries This is one of those features I'd like to get around to sooner rather than later, but I did not do any work on it yet since there are many other things I'd like to get done as well. So feel free to open a pull request for it, I'm looking forward to see your changes!

[EdenIndustries]

@bjorn Ok I'll see what I can do! To my embarassment, I admit Git's notion of branches and pulling and forking and such is not something I'm all that familiar with yet (I've only really used SVN and Perforce), but I'll try to figure it out and get the pull request sorted out :)

[bjorn]

@EdenIndustries Good luck and feel free to ask questions! No need to be embarrassed!

[JesseTG]

@EdenIndustries Try this, it's interactive and very helpful http://pcottle.github.io/learnGitBranching/

[EdenIndustries]

@JesseTG Wow, very cool, thanks!

[JesseTG]

:+1:

[superqix]

@EdenIndustries Did you ever get a branch or PR organized for this?

[EdenIndustries]

Sorry, no. It's been a really busy time for us prepping for GDC and now E3. I can see if I have time to get around to it though. Or if you build Tiled locally, I can just send you the relevant files maybe?

[superqix]

I'd be willing to give it a look. wilson at no2games dot com is probably the easiest way to send it along. Thanks!

[EdenIndustries]

No problem! I'll try to send it along shortly

[damienleroux]

+1 :)

[harrisyu]

+1
Waiting for this for a long time.
Now I need to hide other layer to prevent false selecting.
👍

[ketanhwr]

What exactly will be the features? A layer locked means that we won't be able to edit it, right?

[bjorn]

What exactly will be the features? A layer locked means that we won't be able to edit it, right?

Exactly. Also, a locked group layer means the lock applies to the child layers as well, recursively. See for example Layer::isHidden, which behaves similarly.

One of the things you'll need to do is to find a way to add another interactive icon to each layer in the layers view. We used the checkable state for the visibility, and first of all we could try to do the same by adding another checkable column.