Fix bug #74

[finscn]

Only water-huge2 failed .
the log says :

not ok 18 4464 triangles when expected 4461

I think maybe something is wrong in the test-case.

[finscn]

With this PR , it could solve the problem in #74 :

[mourner]

Cool! Can you describe the logic in more detail here?

[finscn]

the key code is :

        var toRemove = false;

        if (!p.steiner) {
            if (equals(p, p.next) || equals(p.prev, p)) {
                toRemove = true;
            } else if (area(p.prev, p, p.next) === 0) {
                // If `p.prev, p & p.next` are on holes (not outer edge) ,
                // And `p.prev & p` are on the same hole ,
                // Then do NOT remove `p` .
                if (prevHole && nextHole && prevHole !== nextHole && prevHole === currentHole) {
                    toRemove = false;
                } else {
                    toRemove = true;
                }
            }
        }

But there is something I can't understand about

            if (equals(p, p.next) || equals(p.prev, p)) {
                toRemove = true;

if no || equals(p.prev, p) , the test-case in #74 will be failed.

[finscn]

Is there any news about this pr & issue ?

[finscn]

Is there any news about this pr & issue ???

[mourner]

@finscn sorry, I didn't have the chance to thoroughly review it yet. It's on my list. Feel free to use your forked version in the mean time.

[stefnotch]

I don't mean to add useless noise, but I'd be interested if there is a chance of this PR getting merged anytime soon.