speps/LibTessDotNet

Issues

• Performance regression

  #57 opened 2 months ago by anyuser
  0

• Failing on simple example.

  #50 opened 3 years ago by Scrawk
  1

• Tessellation triangle size

  #56 opened a year ago by sjc9999
  0

• Ｉｓ　ｉｔ　Ｓｕｐｐｏｒｔ　ＡＲＭ６４？

  #55 opened a year ago by NTUZZH
  0

• DefaultTypePool requires JIT compilation

  #51 opened 3 years ago by morgoth990
  6

• Subtracting triangle from rectangle with WindingRule.Positive does not work as expected

  #54 opened 2 years ago by sqeezy
  6

• Support for Iterative Tessellation?

  #53 opened 3 years ago by DavidCampbellIII
  0

• Incorrect triangulation

  #13 opened 7 years ago by NMO13
  5

• Why is there no C++

  #49 opened 3 years ago by chenyanglei0418a
  1

• Winding number possibly incorrect

  #47 opened 4 years ago by DanielLorrig
  2

• Pool more types

  #31 opened 4 years ago by speps
  0

• The results of the performance tests

  #44 opened 4 years ago by xiongxingplus
  1

• Can you release it on the nuget?

  #43 opened 5 years ago by mzh3511
  1

• Performance bottlenecks of algorithm or memory?

  #45 opened 5 years ago by Pro100AlexHell
  1

• SUnitX, SUnitY and SentinelCoord documentation?

  #41 opened 6 years ago by BasmanovDaniil
  2

• Tess.Normal setter doesn't do anything

  #39 opened 6 years ago by BasmanovDaniil
  1

• Tess.Tessellate and Tess.AddContour should have XML documentation

  #21 opened 6 years ago by BasmanovDaniil
  1

• MeshUtils.Undef is inaccessible from outside of the library

  #32 opened 6 years ago by BasmanovDaniil
  1

• Method Tess.DiscardExterior is unused

  #29 opened 6 years ago by BasmanovDaniil
  1

• Tess.cs has inconsistent line endings

  #26 opened 6 years ago by BasmanovDaniil
  0

• What is the point of measuring PolyConvert in BenchForm?

  #20 opened 6 years ago by BasmanovDaniil
  1

• pooling & DEBUG_CHECK_BALANCE

  #18 opened 6 years ago by andypoly
  0

• Robustness and collinear points compatibility

  #17 opened 7 years ago by electroremy
  43

• Tessellation error (winding rule not respected)

  #12 opened 7 years ago by faber80
  9

• pool performance (new T) and bugs (not balanced alloc/free)

  #15 opened 7 years ago by Pro100AlexHell
  19

• Not thread safe

  #14 opened 7 years ago by imekon
  3

• BoundaryContours didn't work properly

  #11 opened 9 years ago by lapilesos
  2

• Remove empty statement warning in for loop

  #10 opened 9 years ago by KellanHiggins
  1

• Invalid Elements data using this input

  #8 opened 9 years ago by nockawa
  15

• 64 bits support (moving to double)

  #7 opened 9 years ago by renanyoy
  2

• Zero-width triangles are produced (They have no area as one point is between the two others)

  #6 opened 9 years ago by KellanHiggins
  26

• Overlapped poly sets clipping issue

  #1 opened 9 years ago by sasmaster
  2