[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #57157] [octave forge] (octclip) error running

From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #57157] [octave forge] (octclip) error running `make' for octclip,
Date: Mon, 4 Nov 2019 17:23:13 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 SeaMonkey/2.48

Follow-up Comment #3, bug #57157 (project octave):

_"The sheer amount of clipping functions in the geometry pkg is scary."_

Yeah I agree somewhat. There was also a promising polyclip option based on the
Boost library which was fairly fast but unfortunately not very stable.
Basically there are just two options, clipper and mrf, but I agree the number
of calling functions is large.
In a next geometry package the matlab-compatible function polybool should be
able to wrap it all.

The current geometry package has some bugs due to later changes inside core
Octave. But they're easily solved by downloading the relevant private
functions from the repo, I've fixed various bugs there.
We're all waiting for a new geometry package release; once there I'll release
a new mapping package with many other bug fixes as well. Those new versions
also feature polyline clipping.

shaperead's bounding box option doesn't do any clipping, exactly like the one
from Matlab. Any polygon with a vertex in the bounding box gets included.

I'd appreciate if you could submit an example of dysfunctional clipping using
shaperead.m so I can check it with the next mapping package release.


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]