Mysterix

We can definitely do that, performance is not a limitation anymore (except if we have a very high number of path, but there is still room for code optimization) I...

ok I implemented "option 2" from my previous post. Don't merge it yet, I will test it this afternoon (it's just in case you want to have a look)

ok it works. As it is, users have to do add `iso.draw()` at the end of their previously written code, I don't really know how to achieve perfect backward-compatibility

Following a suggestion by jdan, now it manages backward-compatibility. User code that worked will still work. If you want the new features, you can write it like : ``` var...

That's what I implemented in the last commits (see my comment above, the one that begins with "Following a suggestion by jdan")

You're perfectly right, and there is a solution : It depends on how often you have to hit test compared to how often you have to redraw the scene. If...

There is a benchmark here : http://jsperf.com/ispointinpath-boundary-test-speed/4 where isPointInPath from canvas API performs slower than pointInPoly, I found that surprising, but took the fastest

Of course I don't mind, I tried to answer quickly to your questions, I will try to answer more completely soon, I need to read again the code to refresh...

Sorry misclick, I write it again : Let H be the hyperplane induced by pathA. PathA must be drawn before PathB if at least one of PathB vertices is on...

Problem seems to be solved on my repo (even with jdan's temple from the gallery !) I don't PR it yet because it is still slow (because of the overlap...