-
-
Notifications
You must be signed in to change notification settings - Fork 498
New issue
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
Automatically place layers into the artboard they're drawn inside of #2110
Automatically place layers into the artboard they're drawn inside of #2110
Conversation
Signed-off-by: James Ryans <[email protected]>
Signed-off-by: James Ryans <[email protected]>
Signed-off-by: James Ryans <[email protected]>
Signed-off-by: James Ryans <[email protected]>
Signed-off-by: James Ryans <[email protected]>
377b910
to
3bcefaf
Compare
!build |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Hi @james-ryans, I've just discovered a regression introduced by this PR. Would you be able to work on solving it in a new PR, please? If you're not able to do so in the next few days, please let me know and I'll try to find someone else to work on it, but you're probably the most familiar with the code so it'd be great if you do have the time. Thank you! Problem description: when a nested layer is selected, creating new shapes with the drawing tools should put the new layers alongside (as siblings of) the selected layer. The regression results in those always being drawn at the top level, just inside the artboard (if there is one, otherwise at the document root).
|
@james-ryans Hello, just checking up to see your plans. I saw you reacted to the previous message. Since this introduces a somewhat serious quality-of-life issue for drawing inside of folders, I may revert this PR within the next few days so the original feature can be re-attempted now that we know this is a regression to watch out for (which I failed to find during my initial QA tests). But I'm just commenting to see if, perhaps, you've been already working on a solution and are nearly ready to open a PR for it. In that case, I'll hold off for a few days before reverting. What's best in regards to your plans? Thank you! |
A regression introduced in #2110
Turns out it wasn't overly difficult to fix, so I implemented it myself (in the commit listed in the history directly above this comment) out of concern for timing. Now I can do another production deploy so users can access an editor without this breakage again. When you have more time on your hands to keep contributing, there is plenty available, just ping me and I'm happy to assign more feature requests for you to take a look at. Thanks again for this valuable feature! |
Part of #1507