Comment 6 for bug 473608

Revision history for this message
su_v (suv-lp) wrote :

other possible workarounds:

- Don't use the the 'Align and Distribute…' dialog, align the objects by snapping to guides or grid instead:
- Adjust / fine-tune the snapping options on the Snap Controls Bar
- Switch between visual and geometrix bbox if needed
With geometric bbox you could turn off node snapping and only use bbox snapping. This works for your illustrated example, but would need different settings if the circle object has a stroke as well. Then you might be better of with visual bbox and both types of snapping enabled (bbox and nodes): snap open stroked rectangles with the nodes to the guides/grid, snap closed stroked shapes with the bbox to the guides/grid.

- use a different web slicing method: the recently updated 'Inkscape-Slicer-Extension' (info: <https://bugs.launchpad.net/inkscape/+bug/169985>, download: <http://github.com/mattharrison/Inkscape-Slicer-Extension>) gives you better visual control about the slices and allows overlapping slices as well as omitting possible gaps (at least theoretically - I didn't try it myself since I don't have a more complex or real-world example at hand).

> Anything else I can do on this?
Hire someone who can contribute a patch? ;-)
1) bbox setting ignored for aligning objects:
Making the 'Align and Distribute…' dialog respect the bbox settings might be easier to fix (*maybe* - I'm not a developer myself) than the second bug:
2) visual bbox wrong for butt cap lines:
I think the developers who work on snapping and related modules are well aware of the deficiencies, but some issues are hard to fix (as explained in the above linked reports) or require some broader code refactoring to be finished first (like replacing currently used functions with newer ones from lib2geom). A quote from an (unrelated) bug triggered by bbox issues: «The bigger picture IMHO is that we still need to replace all occurrences of NRRect by Geom::Rect, in each SPItemClass.» <https://bugs.launchpad.net/inkscape/+bug/318726/comments/4>