Summary: | using a shape tool creates new shape layer even if shape layer selected | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Nabil Stendardo <nabil> |
Component: | Filter Layers | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | animtim, halla, mifrosu |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/calligra/d422b5e7331a4a592a68af06e151ad198fff4664 | Version Fixed In: |
Description
Nabil Stendardo
2012-05-11 21:41:40 UTC
Hi Nabil, Thanks for your report. I can confirm the bug. The strange thing is, dragging a shape from the add shape palette doesn't create a new shape layer... *** Bug 301213 has been marked as a duplicate of this bug. *** Following some experimentation using current git master: In addition to dragging from the shape palette, the "draw a path" and the "draw straight line with current brush" tools behave as expected---i.e. add to an existing vector layer rather than creating a new one. Also, copying and then pasting an existing shape within a layer behaves as expected. Git commit d422b5e7331a4a592a68af06e151ad198fff4664 by Sven Langkamp. Committed on 19/07/2012 at 14:40. Pushed by langkamp into branch 'master'. fix inserting of shapes on shape layer with some tools, systemLock was set incorretly patch by Michael O'Sullivan REVIEW:105618 M +1 -0 krita/plugins/tools/defaulttools/kis_tool_ellipse.cc M +1 -1 krita/plugins/tools/defaulttools/kis_tool_rectangle.cc M +2 -0 krita/plugins/tools/selectiontools/kis_tool_select_elliptical.cc M +4 -1 krita/plugins/tools/selectiontools/kis_tool_select_polygonal.cc M +3 -0 krita/plugins/tools/tool_polygon/kis_tool_polygon.cc M +3 -0 krita/plugins/tools/tool_polyline/kis_tool_polyline.cc M +0 -2 krita/ui/tool/kis_tool_ellipse_base.cpp M +0 -2 krita/ui/tool/kis_tool_polyline_base.cpp http://commits.kde.org/calligra/d422b5e7331a4a592a68af06e151ad198fff4664 No it's not fixed. The fix is committed only to the 'master' branch, which means that unless the user wants bleeding-edge code, he does not benefit from the fix. Please backport it. This is by now in Krita 2.6 which is generally available. |