Inkscape.org
Beginners' Questions Cut Path operation without gap
  1. #1
    cqy20952 cqy20952 @cqy20952

    How to perform Cut Path without a gap?

    The gap can be viewed in outline mode.

    Thank you.

     

  2. #2
    Kirstie Kirstie @Kirstie🌷

    Hi,

    I do not understand your question. Can you try say it in other words please?

    You can also add pictures, so that the people that try to help, will understand the question better.

  3. #3
    Lazur Lazur @Lazur

    Hi. 

     

    My guess is you experience the "gap issue". 

    The background will always show through in betweem two objects with perfectly matching shapes due to how anti-aliasing works. 

    You need to either switch off anti-aliasing, 

    or trick the renderer to display more aliased edges -by duplicating the objects atop eachother

    or by adding an outline which cover the edge. 

     

    Personally I prefer to draw things as they were cut off of paper and one piece was glued next to another one -the bottom one overlapping the top one's edge. Can get quite tedious and tricky sometime. It's the necessary line if you aim for pixel perfect drawings.

  4. #4
    brynn brynn @brynn

    Sharing an SVG file which shows the problem can prevent us from guessing.  The 2nd message of this topic tells how to attach an image or file:  https://inkscape.org/forums/questions/how-to-make-a-screenshot-and-put-it-in-a-message/

  5. #5
    cqy20952 cqy20952 @cqy20952
    *

    Thank you for replies and sorry for the short message.

    Suppose I'm creating a leaf.

    I'm going to duplicate the red stroke and cut path over the combined squares.

    After the operation, in outline mode when zoomed, you'll notice the gap at the edge of the leaf.

    Capture
    Capture2
    Capture3
    Capture4
    Capture5
  6. #6
    brynn brynn @brynn

    That's a much wider gap than we would expect.  Can you share the SVG file?  It would be faster than us asking a lot of questions and guessing.

  7. #7
    Tyler Durden Tyler Durden @TylerDurden

    Zoom level is 25600...

  8. #8
    cqy20952 cqy20952 @cqy20952
    *

    Yes, it should be zoomed to the maximum to see the gap.

  9. #9
    Flamingolady Flamingolady @flamingolady🦩

    I tend to do what Lazur does, seems to work the best.  But other workaround methods are to do path offset which usually fills in the gap; or just extend that line a bit.  Sometimes adding a stroke works too; or a path>union or join nodes with a new segment might work.  It just depends on what you are working on.

  10. #10
    cqy20952 cqy20952 @cqy20952

    Thank you for your reply. This gap issue arises after the Cut Path operation. The gap can only be viewed in outline mode at the maximum zoom level. My workaround for this issue is I insert a node in each path intersection, break the node and delete the excess segment. The problem with this technique is that it can be a little bit laborious. 

  11. #11
    Flamingolady Flamingolady @flamingolady🦩

    yes, laborious.  It would be nice if Inkscape had that same feature that Gimp uses where you can change the cut path outline, in or out by however many pixels you want.  Then magically no gap...  wishful thinking!

  12. #12
    Tyler Durden Tyler Durden @TylerDurden
    *

    An infinitesimal gap on a 0.5m drawing? Does that need solving?

     

    Too small to measure without scaling up.  At 100x scaling, it is less than a mm.  Size as originally drawn: 0.0087335803 mm (or <9 microns).

     

    Have a nice day. 

    TD

  13. #13
    Flamingolady Flamingolady @flamingolady🦩

    Tyler, while I agree that it's quite small, it drives me nuts!  To me it's noticeable, it just subliminally pulls the eye to it, esp on a dark background. 

    and ps I've been playing around with the polygon/voronoi diagram tool (there's a vid tut) where you fill in the triangles and delete the outline, which creates a noticeable gap, so if you figure out how to fill in the gap, it works for multiple things.  For me, the path>offset works perfectly to fill it in.

  14. #14
    brynn brynn @brynn

    When I test it, and zoom to the maximum, the gap is much smaller - just the typical anti-alias issue.  I suspect the problem is happening as a result of how cqy20952 performed the operation.  But the possibilities are too many to spend time guessing.  That's why I asked to see the SVG file.

    This is the only guess I will make.  The original leaf shape started out as a circle or ellipse, and we have seen discrepancies with ellipses and path operations in the past.  It's fixed in 1.0 beta, but we don't know what version was used.  If that's not it, I would need to see the SVG file, to sort it out.

  15. #15
    Maren Hachmann Maren Hachmann @Moini

    Maybe try to adjust the numeric precision in the settings? Edit > Preferences > Input/Output > SVG output.

  16. #16
    cqy20952 cqy20952 @cqy20952

    Wow, so it is fixed in 1.0 beta. Ya, the leaf shape started as an ellipse.

  17. #17
    Maren Hachmann Maren Hachmann @Moini

    We don't know if it is fixed. It might just be the numeric precision in your preferences.

  18. #18
    cqy20952 cqy20952 @cqy20952

    I always delete preferences.xml so my preferences are always at default.

  19. #19
    Maren Hachmann Maren Hachmann @Moini

    You can still increase the precision, if you need it to be higher.

  20. #20
    Tyler Durden Tyler Durden @TylerDurden
    flamingolady

    Tyler, while I agree that it's quite small, it drives me nuts!  To me it's noticeable, it just subliminally pulls the eye to it, esp on a dark background.  and ps I've been playing around with the polygon/voronoi diagram tool (there's a vid tut) where you fill in the triangles and delete the outline, which creates a noticeable gap, so if you figure out how to fill in the gap, it works for multiple things.  For me, the path>offset works perfectly to fill it in.

    In the OP's case, there would be no visible gap, as the paths are stroked.

    The voronoi exercise may be a different issue altogether.

  21. #21
    cqy20952 cqy20952 @cqy20952
    😀

    Maxed precision but no luck.

    Just tried using 1.0beta1_2019-09-17 and I think it is fixed.