Comment 0 for bug 808558

With the recent changes (stroke applied before transformation), scaling an object (regular path) with these settings can result in "corrupt" path data:

- visual bbox
- snap nodes or handles to grid
- no stroke scaling
- default snapping preferences

It seems that the 'visual' (now non-uniform) stroke scaling that occurs while dragging the selection handle (AFAIU bug #165727) can result in path data values which cause the canvas/scrollbars to flicker and/or the scaled object to temporarily "disappear". If releasing the mouse in such a moment, the object "disappears" and can no longer be rendered on-canvas properly.

See attached file for such a corrupted scaled path: I started with a closed rectangular path (~100 x 100 px), stroke width 10 px, and scaled it with the mouse by dragging the upper right transformation arrow and letting it snap to the grid (all inside the visible page border i.e. an aera of 400 x 400 px). At some random point the object disappeared and I released the mouse button, and saved the drawing. Open the file, use <TAB> to select the path and try to zoom to selection…

I failed to reproduce it when hiding the grid (all other settings unchanged) - i.e. no snapping occurs while resizing.

Not reproduced with Inkscape 0.48.1, 0.48+devel r10325
Reproduced with latest revision of cairo-rendering branch r9598
and current trunk (revisions tested: r10391, r10932, 10446)
on Mac OS X 10.5.8 (i386)