diff options
| author | bubnikv <bubnikv@gmail.com> | 2016-09-13 14:30:00 +0300 |
|---|---|---|
| committer | bubnikv <bubnikv@gmail.com> | 2016-09-13 14:30:00 +0300 |
| commit | 620c6c7378c4799980f63794669548c104b9bcea (patch) | |
| tree | fc7aea3342539018bb19d27abd1144956eb00b4d /xs/src/libslic3r/ClipperUtils.hpp | |
| parent | a5b7f14dfa291039fd6971a356efd011fab84440 (diff) | |
Ported from the playground branch. Various documentation and optimization.
Diffstat (limited to 'xs/src/libslic3r/ClipperUtils.hpp')
| -rw-r--r-- | xs/src/libslic3r/ClipperUtils.hpp | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/xs/src/libslic3r/ClipperUtils.hpp b/xs/src/libslic3r/ClipperUtils.hpp index e7396af76..ccdf75588 100644 --- a/xs/src/libslic3r/ClipperUtils.hpp +++ b/xs/src/libslic3r/ClipperUtils.hpp @@ -14,6 +14,11 @@ using ClipperLib::jtSquare; namespace Slic3r { +// Factor to convert from coord_t (which is int32) to an int64 type used by the Clipper library. +//FIXME Vojtech: Better to use a power of 2 coefficient and to use bit shifts for scaling. +// How about 2^17=131072? +// By the way, is the scalling needed at all? Cura runs all the computation with a fixed point precision of 1um, while Slic3r scales to 1nm, +// further scaling by 10e5 brings us to #define CLIPPER_OFFSET_SCALE 100000.0 //----------------------------------------------------------- |