We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From my point of you it might be useful to have a named access to the project's layers as one has with named items in a group.
var layer = new paper.Layer({name: 'test'});
// later in code
var theLayer = paper.project['test']; // IMHO this would be nice
currently I am doing:
var theLayer = paper.project.getItem({name: 'test');
// this is ok of course ...
The text was updated successfully, but these errors were encountered:
Yes this can be considered. But if we followed the logic of named access of children on the children lists of their parents, then it would be:
var layer = paper.project.layers['test'];
Sounds good?
I'd like to offer this also for segments...
Sorry, something went wrong.
... sounds good to me. :-)
Unify the way item parents and projects as parents of top-level layer…
406d26e
…s are handled as owners. This automatically adds support for named children on project.layers, closing #491.
This took way too long, but will finally be in the next release.
lehni
No branches or pull requests
From my point of you it might be useful to have a named access to the project's layers as one has with named items in a group.
var layer = new paper.Layer({name: 'test'});
// later in code
var theLayer = paper.project['test']; // IMHO this would be nice
currently I am doing:
var theLayer = paper.project.getItem({name: 'test');
// this is ok of course ...
The text was updated successfully, but these errors were encountered: