(Regression) Bug in Ctrl+scaling of triangle figure under special conditions

[Nizamov Shawkat]

Detected in 0.48-pre1 on Windows, not reproducible with 0.47 on Linux and Windows.

How to reproduce:

1) Start Inkscape
2) Select "Stars and polygons" tool
3) Set "Corners" to 3
4) Pressing Ctrl, draw an equilateral triangle, with bottom oriented strictly horizontal
5) Select "Select and transform objects" tool (arrow)
6) Select created triangle
7) Pressing again Ctrl try to scale it by dragging upper right corner of frame
8) Release mouse button and see how triangle dissappears (or scales to zero size ???)

This funny bug is not reproducible with other figures, with 3 other corners of selection frame or when this figure is just in different orientation. Bug is completely reproducible on my PC.

[su_v (suv-lp)]

Not reproduced with Inkscape 0.47, 0.48pre1 and r9607 (trunk) on OS X 10.5.8
tested both with default (new) preferences and custom preferences.

Can you reproduce it with default preferences?
What are your snapping settings when the error occurs?

[Nizamov Shawkat (nizamov-shawkat)]

I deleted Inkscape profile directory and bug is still reproducible, so it happens with default settings. Snapping settings are also default.
Inkscape version : 0.48-pre1-r9509 on WIndows XP

See screenshots. I drag the corner of the frame with Ctrl pressed in the 1st screenshot. Result is on the second.

[Nizamov Shawkat (nizamov-shawkat)]

I have just installed Inkscape 0.48-pre1 on another WinXP. Bug is also reproducible there

[su_v (suv-lp)]

I'm stumped - there are three builds (two official: 0.48pre1, trunk r9606; one local: 0.48.x r9614) with which I managed to reproduce the bug (not consistently), but with the local build from lp:inkscape trunk (latest is r9607) - experimental LPEs enabled - I haven't been able to reproduce it at all (default prefs, new document from A4 template).

[su_v (suv-lp)]

@JazzyNico - can you test with a trunk build which includes Diederik's latest commit? Is it possible that the snapping refactoring in revision 9607 fixed this? I can reproduce it with e.g. r9424 (local build, same configuration as r9607), but not with r9607.
<http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/9607>

[jazzynico (jazzynico)]

@~suv - Yes, I can reproduce this bug on Ubuntu 10.04 with the 0.48.x branch, but it is fixed in the trunk .

[su_v (suv-lp)]

Updating bug status to reflect comment #7: «I can reproduce this bug on Ubuntu 10.04 with the 0.48.x branch, but it is fixed in the trunk»