I'm trying to make a honeycomb lattice. I tried following both versions of the instructions here but I end up with overlapping. How do I achieve the lattice? I don't know how to predict the result of the values entered into the tiled cloning interface.

Yeah, that's the problem with tiled clones is that you pretty much have to be a math or geometry whiz, to be able to use it. By the time I figure out the right numbers to use, I could have "manually" duplicated and snapped together a whole page.

In the example you showed, the author has his hexagon flipped around so that the top is horizontal. You've done it with a point at the top. So you'll need some different values for the Shift tab.

I couldn't tell you what they are, without spending a bit of time on it. But someone else may know the exact values already, and might post them for you.

I'm no math wiz, but if you stick two hexagons together you can "read" the needed shifts.

The horizontal offset will need to be 50% per column to nest.
Since the height of each "point" (top and bottom) is 25% the height of the vertical sides, the vertical (y-shift) needs to be +75% (or negative).
Each column also needs to have 50% space between hexagons if we are nesting... they can''t be point to point in the same column. So each row needs 50% y-shift.


One important note: tiling reads the original object's bounding box, so if you want the paths to touch node to node, build the tiles without stroke, then add the stroke to the original after the tiles are made.

Another direction (from the manual)

http://tavmjong.free.fr/INKSCAPE/MANUAL ... Shift.html

<offtopic> TD, how do you create those zoomed-in screenshots of dialogs on Windows? </offtopic>

I use sharex (Foss) : https://getsharex.com

Thanks, TD (I just figured out a different solution, making use of a hidden VirtualBox setting, now my screenshots are going to be twice as large for the manual )

LOL, wish that were possible, Lazur

Off topic:

Oh, didn't think of tracing... A bit too much work for that manual, and too heavy files for serving on the web - especially given that booktype (the software that is used for writing the manual) doesn't even accept SVG. But when vector screenshots become a possibility, with Gtk3, and we can build the manual ourselves in a git repository, then I'd love to have SVG.