Timeline for Strange behavior of Polygon with a hole
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 14 at 12:28 | comment | added | qwerty | I thank you both for very thought-provoking discussions. | |
| Sep 14 at 12:10 | comment | added | azerbajdzan | The point is that the error is not on the user's side as the user provided input in the most accurate form. The error is on the side of the software. Anyway your answer is useful as a workaround. | |
| Sep 14 at 12:00 | comment | added | Domen |
@azerbajdzan, generally, there is no such thing as exact when doing numerical computations. There are various types of numerical errors, which can lead to wrong results. Obviously, I don't have a proof that this is the real reason here, just my hunch. Note that Rationalize has absolutely no effect here, because rendering is not done with exact arithmetics.
|
|
| Sep 14 at 10:16 | comment | added | azerbajdzan |
OP points are NOT "nearly coplanar". They are coplanar exactly. You can replace the coordinates with exact values by applying Rationalize and the bug still persist.
|
|
| Sep 14 at 10:09 | history | answered | Domen | CC BY-SA 4.0 |