Great, thanks Jabier!
Am 29.12.2017 um 13:33 schrieb Jabier Arraiza:
Hi Eduard, I just make a MR. with this fix.
https://gitlab.com/inkscape/inkscape/merge_requests/166
Regards, and thanks for the inputs.
Jabier.
-----Original Message----- From: Eduard Braun <eduard.braun2@...173...> To: jabier.arraiza@...2893..., Inkscape-Devel <inkscape-devel@...1240... ceforge.net> Subject: Re: [Inkscape-devel] Survey: Default beabiour on clones with path operations Date: Sat, 16 Dec 2017 12:46:39 +0100
Am 16.12.2017 um 12:39 schrieb Jabier Arraiza:
On Sat, 2017-12-16 at 12:10 +0100, Eduard Braun wrote:
Am 16.12.2017 um 11:55 schrieb Jabier Arraiza:
On Fri, 2017-12-15 at 22:07 +0100, Eduard Braun wrote:
P.S. Just noticed some path operations do not unlink yet:
- Inset / Outset
- Dynamic / Linked Offset
- Simplify
- Reverse
Should they unlink, too? I don't see a reason why not...
Also I can not apply a path effects to clones - is that "by design"? If I try "Clone original" is applied automatically (without a possibility to choose another path effect) but seems to be non- functional...
I do it soon. About path effect part, I think we need more discussion. Realy not sure about, maybe can be another pref option by default to false?
Thanks.
Thanks!
Regarding path effects: It's certainly not required but the current behavior confused me. Why is there a "Clone original" inserted as soon as I click "Add path effect"? Also after that my path is gone - that seems wrong... Maybe just do nothing in this case and show a warning if the user attempts to apply a path effect to a clone (like we did for other objects before and like we still do if the new setting is disabled)?
Regards, Eduard
Removing this clone path effect destroy the clone :( Realy the desirable to me work is:
- Clone -> add path effect -> apply clone path effect.
- Allow add more LPE after it
- When remove clone LPE the clone go up.
Put it on my TODO if we find consensuous.
Regards.
Ah, I see... that's how it's supposed to work! The way you describe sounds perfectly reasonable, just wasn't sure if I hit a bug here or even undefined behavior...