-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of J.B.C.Engelen@...1578... Sent: dinsdag 8 april 2008 22:19 To: buliabyak@...400... Cc: inkscape-devel@lists.sourceforge.net; Bastien.Bouclet@...1940... Subject: Re: [Inkscape-devel] LPE internals - conversions
-----Original Message----- From: bulia byak [mailto:buliabyak@...400...] Sent: dinsdag 8 april 2008 22:11 To: Engelen, J.B.C. (Johan) Cc: inkscape-devel@lists.sourceforge.net; jf.barraud@...400...; steren.giannini@...400...; Bastien.Bouclet@...1940...; Anhalter42@...173... Subject: Re: LPE internals - conversions
On Tue, Apr 8, 2008 at 4:32 PM,
<J.B.C.Engelen@...1578...> wrote:
- Take two separate paths and combine them into one
(ctrl+k) 2.
draw a circle, convert to path, copy it 3. apply
lpe-Pattern Along
Path to (1) and paste the circle as pattern 4. the result
will be two
circle halves. where actually I would have expected to see
two circles, since it looks like the original path is 2 paths.
This is undesired behavior I think. Note that e.g.
lpe-Gear also suffers from this: it just seems to ignore the second path.
Do people consider this as a bug, or as a feature?
It is indeed a bug, and I reported it, and it was fixed in
svn. So in
revision 18266 this produces two visible separate circular
brushes on
two subpaths. Which version you're testing?
doh! I just tested and you are right. I remembered it from some time ago and went to fix it without testing whether the bug was still present. Thanks JFB for fixing it, but I am going to fix it another way! ;)
OK, so then I'll just go ahead and change the way the doEffect chain works. I'll check the other effects first, but at least it should fix the gear lpe.
I have changed the way the doEffect chain works. For old behavior put this in the constructor: concatenate_before_pwd2 = true; (which is done in lpe-bendpath.cpp for example)
Read a bit more details about it here: http://wiki.inkscape.org/wiki/index.php/MakingLivePathEffects#Write_your_eff... Or just study Effect::doEffect_path.
Regards, Johan