Inkscape 0.91: measuring tool can´t measure several paths at once any longer

Bug #1429932 reported by Arnold on 2015-03-09
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Inkscape
Medium
Alvin Penner

Bug Description

I updated my workaround to Inkscape 0.91 (64-bit-Version) on a WIN 8.1 machine. When I mark several paths at once and try to measure them with ->Extensions->visualize path->measure path, I only receive a measure for the first marked path. All the other paths are labeled with "0,00"

su_v (suv-lp) wrote :

Not reproduced with Inkscape 0.91 r13725 on OS X 10.7.5 (locale: en_US.UTF-8): the 'Measure path' extension produces the same expected result if applied to a selection of multiple lines as Inkscape 0.48.5 (each path is measured and labeled separately and correctly).

Please attach a test case (Inkscape SVG) file with paths which reproduce the reported issue.
Which locale settings and menu language do you use?

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

Not reproduced on Windows XP, Inkscape 0.91 and trunk rev. 13986.

Per Gustafsson (per-g-t) wrote :

I have the same problem with Inkscape 0.91 r13725, Windows 7 professional sp1

su_v (suv-lp) wrote :

Reproduced with Inkscape 0.91 r13725 and 0.91+devel r14178 on OS X 10.7.5 - results are incorrect (randomly smaller AFAICT) except for the first generated label if units other than 'px' are used.

Steps to reproduce:
1) launch inkscape
2) draw horizontal line
3) duplicate and move line several times
4) select all > measure path

Only with 'px' the result is as expected - with any other unit, just the first (in stack order) created measurement label has the expected value, the rest seem to have random values (or '0'), unrelated to the length of the path they are put on.

Not reproduced with Inkscape 0.48.5.

Changed in inkscape:
milestone: none → 0.92
status: Incomplete → Confirmed
tags: added: regression
Changed in inkscape:
importance: Undecided → Medium
su_v (suv-lp) wrote :

Possible fix (use local variable for factor per node inside selection loop - line 197 probably could be moved out of the loop altogether).

Alvin Penner (apenner) wrote :

yes, I think moving this code out of the loop entirely sounds like an excellent idea, not entirely sure why it was there in the first place.
What do you think of the following patch? I haven't tested it very extensively, but it passed my preliminary test okay.

su_v (suv-lp) wrote :

@Alvin - 'measure_fix.diff' tested ok for me with 0.91 and 0.91+devel r14178. I think it is the better solution (to move the code outside the loop).

Changed in inkscape:
status: Confirmed → Triaged
Alvin Penner (apenner) wrote :

good to hear. fix committed to rev 14182

Changed in inkscape:
status: Triaged → Fix Committed
su_v (suv-lp) on 2015-05-28
Changed in inkscape:
assignee: nobody → Alvin Penner (apenner)
tags: added: backport-proposed
su_v (suv-lp) wrote :

Fix backported to 0.91.x in rev 13796.

Changed in inkscape:
milestone: 0.92 → 0.91.1
tags: removed: backport-proposed
jazzynico (jazzynico) on 2017-01-28
Changed in inkscape:
milestone: 0.91.1 → 0.92
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