Moving a partly erased object extracts and shifts eraser stroke

[Alexandre Prokoudine]

1. Draw a rectangle
2. Erase an area inside it
3. Switch to Selector
4. Start moving the object
5. Eraser stroke extracts from it and moves to the right

Same thing happens when you copy/paste such an object. This case is illustrated in the attached file.

[Marcin Floryan (mfloryan)]

Yes. I can see the same behaviour. Setting to confirmed.

[Quasar Jarosz (quasar-ja)]

I cannot reproduce this bug under Windows (SVN 18485). Eraser functions exactly as i would expect it to on a rectangle, and the rectangle can be moved with no issues.

[sas (sas-sas)]

I can't reproduce this either (Windows XP + SVN revision 18483). Does it depend on some preference setting?

[MenTaLguY (mental-deactivatedaccount)]

The only thing I could imagine is if it is possible to move the object in
between the time the erasing gesture is completed and the time the erasure
is actually applied to the path via a boolean operation. In that case I
suppose you could have something like erasure -> move -> erasure in wrong
place, but even then it would only be during a very narrow window of time
before the erasure was "committed".

[Rygle (rygle)]

Can't reproduce on Win32 SVN 14846.

Is this platform specific? Alexandre and Marcin, what platform are you guys using? Is there something that's been missed in build files for Linux? Similar to the Makefiles.am in the /share/extensions directory that is used by Linux, but not by Win32 build.

[Jon A. Cruz (jon-joncruz)]

It appears to be from the current state of calligraphy tool, or leftover settings.

Sounds like it's something to take care of overall with all settings.

[jazzynico (jazzynico)]

Not reproduced on Windows XP (0.47) and Ubuntu 9.10 (0.47pre4).
Could you please confirm that you still have this bug (or not)?

[su_v (suv-lp)]

not reproduced with Inkscape 0.47-1 and r8888 on OS X 10.5.8,
tested both with existing and default preferences.

[jazzynico (jazzynico)]

Alexandre, could you please confirm that this bug is fixed for you now?

[jazzynico (jazzynico)]

Seems to be fixed in 0.47.
Don't hesitate to reopen if you still run into the same issue with a recent version.