![]() > After re-entering the same size a second or even more times, the > bar, the new size seems to be an approximation of the requested size. > When I resize a group by entering a new width or heigth in the icon. > I'm running inkscape 0.45.1-1 on Debian Lenny. > Status in Inkscape: A Vector Drawing Tool: > resize of object or group by entering a numeric size results in a ![]() > You received this bug notification because you are subscribed to a > I have download 0.49.it's work but how could i implement same thing in > you, so why bother if you have already access to v0.49? But why would you want to do that? I feel > v0.48.2? In principle that could be done, if you know a little bit of > You mean that you would like to backport the code from v.0.49 to On Tue, at 11:20 PM, Diederik van Lierop > wrote: It possible to solve in 0.48 version with any patch.?īecause i have done so many change as per my requirement in source code ofĠ.48 version so now days migration of 0.49 version to 0.48 it's more Yes i understand, but my mean is that this bug solve in 0.49 version but is When the stroke width of the objects is zero, the problem does not occur. After releasing the mouse button, the new dimesions are different from the last values shown. While dragging, the W & H boxes show the new sizes. The problem also occurs when resizing using the object handles. Re-entering the desired sizes a few times results in progressively better approximations. The group now has different sizes than entered. Perform the resize by entering values in the W & H boxes in the icon-bar (see picture 'resize.png' included with the original report) Draw a second object (needed to be able to create a group use non-zero stroke width) Set its stroke width to something non-zero (preferably not too small) I can reproduce it using the following steps: The problem occurs when an object which determines one or more of the boundaries of the group has a non-zero stroke width. ![]() I have retested with version 0.46 on debian Lenny.Īfter some experimentation I have narrowed it down to a problem related to the stroke width. ![]()
0 Comments
Leave a Reply. |