Intuitive erasing
Closes !49 (closed).
Merge request reports
Activity
added 36 commits
-
559a14fa...a64f99f5 - 35 commits from branch
master - bd37c8dd - Merged replacing old render function
-
559a14fa...a64f99f5 - 35 commits from branch
added 1 commit
- eecd4a1c - Cache svg cursor, use curveBasis for interpolation
added 1 commit
- 043f6d41 - Refactor distance handling in src/erasure.js
- Resolved by Nayeem Rahman
Ready for review.
@im2517 Big refactor of
src/canvas.js. Most of it is to make it more pipelined and modular, you can see this inrenderPath().Still need to merge with current master.
- Last reply by Nayeem Rahman
added 45 commits
-
7c7039dc...d8498bd5 - 44 commits from branch
master - 9c5ea0cb - Merge remote-tracking branch 'upstream/master' into intuitive-erasing
-
7c7039dc...d8498bd5 - 44 commits from branch
@ml5717 I think we should just merge this and maybe patch in the previous erasing behaviour before we have to demo it. This is going to be hard to keep in sync.
@ml5717 Also, I've implemented the pressure bounding behaviour I was talking about here.
@ml5717 Regarding the frontend side of erasing (though maybe it concerns the backend too), remind me why it's insufficient to erase by drawing over with the background colour?
Ooh, what about clip paths?
Also https://stackoverflow.com/questions/11404391/invert-svg-clip-show-only-outside-path
Edited by Nayeem Rahman
