Typed in measurments in W and H boxes. Numbers change.

[Brian]

(ALL MEASUREMENTS IN INCHES) *Running version 0 . 48 . 5 of inkscape* **running windows 7 home premium 64 bit**

I was trying to make a 12 x 12 square by typing in the measurements in the W and H boxes on top of the screen.

When I pressed enter in the either box the number went from 12.000 to something like 13.061 or 11.990. It does

this 2 or 3 times until 12 shows in either the W or H box.

Thanks in advance.

[Brian (brian-schaefer-88)]

Just an update:

When I select visual bounding box in the preference window it works fine. When I select geometric bounding box that's when the random numbers happen.

[Brian (brian-schaefer-88)]

Sorry about the triple post. I don't know where to edit my earlier posts (if someone could tell me I would appreciate it).

I just now noticed that if geometric bounding box is selected and your object has a fill it gives off the random numbers.

If you don't have fill and selected geometric bounding box it works fine. If you have visual bounding box, whether or not you have

fill, it works fine.

Again sorry for the multiple posts.

[su_v (suv-lp)]

Are you sure that it is the presence of the _fill_ which triggers the reported issue (in geometric bounding box mode)?

There is a well-known issue with the geometric bounding box mode, and the presence of a _stroke_ (fill is not relevant), when scaling the bounding box of the selection via width & height entries on the controls bar of the select tool. This known issue is already tracked in
- Bug #212768 “Geometric and Visual bounding box and object dimensions ”
  <https://bugs.launchpad.net/inkscape/+bug/212768>
(see also other duplicate report bug #398715, and other related reports mentioned in the comments of both reports).

I fail to reproduce the issue with Inkscape 0.48.5 as described in comment #2 - whether or not the object has a _fill_ (e.g. a solid paint color) has no effect on the precision of the scaling of the bounding box in geometric bounding box mode.

[Brian (brian-schaefer-88)]

My bad. I meant stroke :P.

[su_v (suv-lp)]

Thanks for the feedback - in this case it's the same as already tracked in bug #212768 and other earlier reports mentioned in the comments there. Current stable Inkscape 0.48 is known to be affected by it; the next major release 0.91 will include a fix.

Linking as duplicate to bug #212768 - please add a comment here (bug #1357648) and revert the duplicate status if you disagree and think this was done in error.