tbinias / libarea Goto Github PK

I ran into this one while trying to build r77

Curve.cpp: In member function ‘void CCurve::Break(const Point&)’:
Curve.cpp:393: error: no matching function for call to ‘std::list<CVertex, 
std::allocator<CVertex> >::insert(std::_List_const_iterator<CVertex>&, 
CVertex&)’
/usr/include/c++/4.4/bits/list.tcc:97: note: candidates are: 
std::_List_iterator<_Tp> std::list<_Tp, 
_Alloc>::insert(std::_List_iterator<_Tp>, const _Tp&) [with _Tp = CVertex, 
_Alloc = std::allocator<CVertex>]
/usr/include/c++/4.4/bits/stl_list.h:1027: note:                 void 
std::list<_Tp, _Alloc>::insert(std::_List_iterator<_Tp>, size_t, const _Tp&) 
[with _Tp = CVertex, _Alloc = std::allocator<CVertex>]
gcc -c kbool/src/graph.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o graph.o
Curve.h: In constructor ‘Span::Span()’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.cpp:590: warning:   when initialized here
Curve.cpp: In member function ‘Point Span::MidParam(double) const’:
Curve.cpp:653: warning: unused variable ‘radius’
gcc -c kbool/src/graphlst.cpp -Wall -I/usr/include `python-config --includes` 
-I./ -I./kbool/include -g -fPIC -o graphlst.o
make: *** [Curve.o] Error 1
make: *** Waiting for unfinished jobs....

When driving libarea with Python, it's a bit of a pain to add a straight 
segment to a curve.  You end up with something like:
   c.append(Vertex(0, p1, pz))
where 'pz' is never used, and '0' specifies a straight segment.

With the attached patch, this can be written instead as
   c.append(Vertex(p1))

We should be able to recognize arcs in the output.
Currently doing an operation ( like offset ), that makes arcs ( or what
look like arcs ), actually makes lots of little lines.

We need a way of specifying multiple curves for an area, including nested
curves ( islands ). I think this might be demonstrated in one of the
examples that came with the original
http://boolean.klaasholwerda.nl/download/download.html

This issue was created by revision r111.

libarea repository contains two implementations for the same interface with are 
not fully compiliant for all needs:
ie. HeeksCAD uses Clipper implementation (Boolean do not cover all functions) 
and HeeksCNC (through python module) uses Boolean implementation.

This is a bit messy to provide a python module which does not use the same 
implementation as the library does.

What steps will reproduce the problem?
1.I try to set area by myself and to run pocket code.
2.Change some code for run.
3.It only outputs one cycle.

What is the expected output? What do you see instead?


What version of the product are you using? On what operating system?


Please provide any additional information below.
My testing code is in attachment with BCB 6.0

I've noticed that under certain conditions, a pocket operation doesn't fully 
clear the space.  

For a test in HeeksCNC, create a sketch 16mm square and pocket it with a 6.35mm 
cutter.  Set the step over to 5mm.

Set the stepover to 4.75mm and it will be cleared.  

Leave it at 5mm but use a zigzag path and it will be cleared as well.  It seems 
like there's an error in the algorithm for calculating the last pass

http://ubuntuone.com/19CWx6SWRYsOY4WV1nXN3o
http://ubuntuone.com/7EodcXp92Epbbnxgx9rjym
http://ubuntuone.com/34Va1Mzm7Sj7JEdwVAy6Y7

Download source and compile

gcc -c Arc.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o Arc.o
gcc -c Area.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o Area.o
In file included from Area.h:8,
                 from Area.cpp:5:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
gcc -c AreaBoolean.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o AreaBoolean.o
In file included from Area.h:8,
                 from AreaBoolean.cpp:5:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
gcc -c AreaDxf.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o AreaDxf.o
In file included from Area.h:8,
                 from AreaDxf.cpp:6:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
AreaDxf.h: In constructor ‘AreaDxfRead::AreaDxfRead(CArea*, const char*)’:
AreaDxf.h:17: warning: ‘AreaDxfRead::m_area’ will be initialized after
AreaDxf.cpp:8: warning:   base ‘CDxfRead’
AreaDxf.cpp:8: warning:   when initialized here
gcc -c AreaOrderer.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o AreaOrderer.o
In file included from Area.h:8,
                 from AreaOrderer.cpp:6:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
gcc -c AreaPocket.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o AreaPocket.o
In file included from Area.h:8,
                 from AreaPocket.cpp:5:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
gcc -c kbool/src/booleng.cpp -Wall -I/usr/include `python-config --includes` 
-I./ -I./kbool/include -g -fPIC -o booleng.o
gcc -c Circle.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o Circle.o
gcc -c kurve/Construction.cpp -Wall -I/usr/include `python-config --includes` 
-I./ -I./kbool/include -g -fPIC -o Construction.o
kurve/Construction.cpp: In constructor ‘geoff_geometry::Circle::Circle(const 
geoff_geometry::Point&, const geoff_geometry::Point&)’:
kurve/Construction.cpp:369: warning: suggest parentheses around assignment used 
as truth value
kurve/Construction.cpp: In constructor ‘geoff_geometry::Plane::Plane(double, 
const geoff_geometry::Vector3d&)’:
kurve/Construction.cpp:789: warning: suggest parentheses around assignment used 
as truth value
gcc -c Curve.cpp -Wall -I/usr/include `python-config --includes` -I./ 
-I./kbool/include -g -fPIC -o Curve.o
In file included from Curve.cpp:3:
Curve.h: In constructor ‘Span::Span(const Point&, const CVertex&, bool)’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.h:53: warning:   when initialized here
Curve.cpp: In member function ‘void CCurve::Break(const Point&)’:
Curve.cpp:393: error: no matching function for call to ‘std::list<CVertex, 
std::allocator<CVertex> >::insert(std::_List_const_iterator<CVertex>&, 
CVertex&)’
/usr/lib/gcc/i686-pc-linux-gnu/4.4.4/include/g++-v4/bits/list.tcc:97: note: 
candidates are: std::_List_iterator<_Tp> std::list<_Tp, 
_Alloc>::insert(std::_List_iterator<_Tp>, const _Tp&) [with _Tp = CVertex, 
_Alloc = std::allocator<CVertex>]
/usr/lib/gcc/i686-pc-linux-gnu/4.4.4/include/g++-v4/bits/stl_list.h:1027: note: 
                void std::list<_Tp, _Alloc>::insert(std::_List_iterator<_Tp>, 
size_t, const _Tp&) [with _Tp = CVertex, _Alloc = std::allocator<CVertex>]
Curve.h: In constructor ‘Span::Span()’:
Curve.h:51: warning: ‘Span::m_v’ will be initialized after
Curve.h:49: warning:   ‘bool Span::m_start_span’
Curve.cpp:590: warning:   when initialized here
Curve.cpp: In member function ‘Point Span::MidParam(double) const’:
Curve.cpp:653: warning: unused variable ‘radius’
make: *** [Curve.o] Error 

Thanks,
Eugenio.

What steps will reproduce the problem?
1.Install HeeksCNC 0.22.0
2.Execute HeeksCNC
3.Open the pocket0.3\test.dxf

What is the expected output? What do you see instead?
I expect it should show me a image,but it shows nothing.
I can see the image in other softwares(like ABViewr). 

What version of the product are you using? On what operating system?
My operating system is windows XP.

libarea might be useful for additive machining (reprap) in-filling but would 
require a couple changes.  The changes however might also be useful in 
traditional CNC pocket operations.  

First, the fill pattern would need to zig zag across the pocket instead of 
forming concentric circles or spiraling in.

If that can be done, the tool-path on alternating layers needs to be 
perpendicular to each other  This is so that filaments don't end up stacked and 
provide a weak point for splitting.

In the shell, execute
    PYTHONPATH=.libs python -c 'import area; area.Area().Offset(1.0)'

The snippet should execute without error.  However, it encounters an assertion 
error instead:
python: kbool/src/graph.cpp:236: void Graph::AddLink(Node*, Node*, int): 
Assertion `begin && end' failed.
Aborted

Other operations such as Subtract also give similar errors when either
of their inputs are degenerate.

(I am using SVN revision 62 on 64-bit Ubuntu 10.04, but I have no reason to 
believe this is architecture-dependent)

The attached patch makes operations on degenerate Areas non-fatal, and appears 
to give expected results for the cases I've tested.

What steps will reproduce the problem?
1. compile pocket with the latest libarea
2.
3.

What is the expected output? What do you see instead?
Expected: compile without errors.
Instead: a lot of error messages during compile, because data structures in 
libarea are changed without adjusting pocket (mostly dxf.cpp) to these changes.

What version of the product are you using? On what operating system?
Latest libarea checkout, latest visual c++, but this also happens with other 
c++ compilers (MinGW)

Please provide any additional information below.

In Linux build, there are loads of compiler warnings.

Fix them.

In this function,I only see "if(a1->m_curves.size() == 0)
    return;" to break this function.

But I do not know when it will be true.
Does there any parameters or conditons to set?

thank you.

Add Intersect, Unite, Xor functions to CArea, the same as the existing
Subtract function.
Also add the Python wrappers.

What steps will reproduce the problem?
1. compiling in ubuntu 10.04
2.
3.

What is the expected output? What do you see instead?

should compile. instead I get an error


What version of the product are you using? On what operating system?
version 54 on ubuntu 10.04


Please provide any additional information below.
The following is a cut and paste from the terminal upon compile

steve@steve-laptop:~/HeeksCAD/HeeksCNC/libarea$ sudo make install
g++ -shared -rdynamic `python-config --ldflags` -lboost_python-mt -fPIC 
-Wl,-soname,libarea.so.0 Arc.o Area.o booleng.o Circle.o graph.o graphlst.o 
instonly.o line.o link.o lpoint.o node.o PythonStuff.o record.o scanbeam.o -o 
.libs/area.so -lstdc++ `python-config --libs`
/usr/bin/ld: cannot find -lboost_python-mt
collect2: ld returned 1 exit status
make: *** [.libs/area.so] Error 1