mirror of
https://github.com/OrcaSlicer/OrcaSlicer.git
synced 2026-10-05 14:51:06 +00:00
Hanif Koh
e540bbcf35
Generated with include-what-you-use and applied conservatively. Only OrcaSlicer's own headers, the ones under src/ and tests/, are removed or forward-declared; standard-library and third-party includes are left alone. An include is removed only when both the Release and the Debug configuration leave it unused, never from inside a conditional block, and never from a file with platform-specific blocks, which only gain includes. Files whose only use of a header sits behind a feature or debug macro (libvgcode's OpenGL ES and marker code, the ARACHNE/TESTS_EXPORT_SVGS debug output) keep their includes. clonable_ptr.hpp gains #pragma once; it had no include guard and was only safe while Config.hpp was its sole includer.
41 lines
1.1 KiB
C++
41 lines
1.1 KiB
C++
#ifndef slic3r_Fill3DHoneycomb_hpp_
|
|
#define slic3r_Fill3DHoneycomb_hpp_
|
|
|
|
#include <map>
|
|
#include <utility>
|
|
|
|
#include "../libslic3r.h"
|
|
|
|
#include "libslic3r/ExPolygon.hpp"
|
|
#include "FillBase.hpp"
|
|
#include "libslic3r/Point.hpp"
|
|
#include "libslic3r/Polyline.hpp"
|
|
|
|
namespace Slic3r { class Point; }
|
|
|
|
namespace Slic3r {
|
|
|
|
class Fill3DHoneycomb : public Fill
|
|
{
|
|
public:
|
|
Fill* clone() const override { return new Fill3DHoneycomb(*this); };
|
|
~Fill3DHoneycomb() override {}
|
|
|
|
// note: updated 3D Honeycomb doesn't need bridge flow because the
|
|
// pattern is placed on top of previous layers
|
|
bool use_bridge_flow() const override { return false; }
|
|
bool is_self_crossing() override { return false; }
|
|
|
|
protected:
|
|
void _fill_surface_single(
|
|
const FillParams ¶ms,
|
|
unsigned int thickness_layers,
|
|
const std::pair<float, Point> &direction,
|
|
ExPolygon expolygon,
|
|
Polylines &polylines_out) override;
|
|
};
|
|
|
|
} // namespace Slic3r
|
|
|
|
#endif // slic3r_Fill3DHoneycomb_hpp_
|