Summary: | Cannot edit text shape after saving in a vector library | ||
---|---|---|---|
Product: | [Applications] krita | Reporter: | Tiar <tamtamy.tymona> |
Component: | Layers/Vector | Assignee: | Krita Bugs <krita-bugs-null> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | ahab.greybeard, sovrack |
Priority: | NOR | ||
Version First Reported In: | 5.2.9 | ||
Target Milestone: | --- | ||
Platform: | Appimage | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Example Vector Library with a text shape |
Description
Tiar
2020-09-16 12:59:23 UTC
I can understand David's concern about ungrouping pre-existing groups in the vector library but I don't think this would happen if there was an auto-ungroup applied to content after it was dragged out of the library docker and onto the canvas. An addition level of grouping is applied to the object after it's been dropped onto the canvas and seems to be an efficient way of applying a positional offset, depending on where it's been placed on the canvas. An auto-ungroup would result in a small computational load to move the offset values into the lower level of grouping (or into the object itself in the case of an initially ungrouped single object). For a vector library symbol block, internally there may be an additional level of grouping imposed by whatever application has been used to create the vector library but it is possible to have a single ungrouped vector object in a symbol block. Hence auto-ungrouping of any dragged out vector object would work for text (that was not grouped in the symbol block) and would not affect the grouping of other types of library content. Checking for any existing lower levels of grouping and deciding if it's safe or appropriate to remove them is a separate thing and would be complicated. Bug 396945 mentions issues with editing a shape that got grouped and needs to be ungrouped before editing. *** Bug 396945 has been marked as a duplicate of this bug. *** Re-confirmed for 5.2.9. I don't think this is a bug, however, but since others have taken a look at this report and confirmed it I will leave it as such. There is probably no best way to solve this with how Krita treats groups right now, as it's impossible to determine the intentions of elements and their order in a symbol. A text element isn't necessarily the foreground of a symbol or meant to be edited. I would suggest taking inspiration from draw.io (FOSS) and how group objects are handled there. In draw.io a user can navigate into groups and subgroups just by clicking on the elements inside them. A user can also double click an element within a group and subgroups to edit it directly. |