Interpolate extension creates wrong stroke width

Bug #1586568 reported by Hachmann on 2016-05-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Low
su_v

Bug Description

Using the interpolate extension in Inkscape 0.92pre1 from May 27th 2016, I get unexpected path widths when I interpolate two objects (with the same path width or not, no matter if the interpolate style option is selected). The width is roughly 26% of the initial width.
Using mm as document unit.

(Edit: Unrelated and covered by another report already: The extension also seems to create open paths out of my closed paths. This happens in 0.91, too, if I'm using the same path (copy-pasted from 0.92pre1 to 0.91).)

Hachmann (marenhachmann) wrote :
description: updated
su_v (suv-lp) wrote :

The 'closed paths are opened' issue is unrelated to the units issue and likely already covered by:
* Bug #202540 “Modify path effects open closed paths”
  https://bugs.launchpad.net/inkscape/+bug/202540
(a limitation of the cubicsuperpath module which currently does not preserve 'Z' path commands)

If not covered by bug #202540, or if it can be fixed without refactoring csp, this aspect needs to be filed and tracked separately.

tags: added: extensions-plugins units
Hachmann (marenhachmann) wrote :

Thanks, V, I'll update the description.

description: updated
summary: - Interpolate extension creates wrong stroke width, open paths
+ Interpolate extension creates wrong stroke width
su_v (suv-lp) wrote :

Patch to fix interpolating stroke widths - please test.

Hachmann (marenhachmann) wrote :

That works very well for me, thank you, V!

su_v (suv-lp) wrote :

@JazzyNico - please milestone to 0.92 (it's not strictly a regression: while already present in 0.91, the incorrect stroke width interpolation is not exposed with default new documents there).

Changed in inkscape:
status: New → Confirmed
jazzynico (jazzynico) wrote :

Milestoned to 0.92.
And more patch to test and commit in my long todo list.

Changed in inkscape:
milestone: none → 0.92
assignee: nobody → jazzynico (jazzynico)
importance: Undecided → Low
status: Confirmed → In Progress
Jabiertxof (jabiertxof) wrote :

@jazzynico ping me if you want help, when you want.

jazzynico (jazzynico) wrote :

@Jabier - Thanks! Most of my tasks are related to documentation, translation and extensions, plus some patch that need to be tested. Don't hesitate to try this one or others attached to other reports linked to 0.92. The more we test, the better it is!

Apart from it, it would be really great if every developer could review the reports related to their favorite part of the Inkscape code and try to fix some of them (preferably crashes and regressions). Inkscape already has lots of features, but needs some polish now. I'm pretty sure there are some LPE bugs you could fix (there are currently 54 open bug tagged LPE, 11 are high importance and 5 are regressions -not all recent). Would you be willing to take a look?

Jabiertxof (jabiertxof) wrote :

Yes this weekend go into!

jazzynico (jazzynico) wrote :

Patch successfully tested on Xubuntu 16.04, Inkscape 0.92.x rev. 15048 and trunk rev. 15080.

jazzynico (jazzynico) wrote :

and committed in the 0.92.x branch (rev. 15049) and trunk (rev. 15081).

Thanks for the patch, su_v!

Changed in inkscape:
assignee: jazzynico (jazzynico) → su_v (suv-lp)
status: In Progress → Fix Committed
Bryce Harrington (bryce) on 2017-01-10
Changed in inkscape:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Bug attachments