Closed GoogleCodeExporter closed 8 years ago
Is your new error just related to pocketing? You might want to make sure you
have an up to date version of libarea.
Original comment by ddfalck2...@yahoo.com
on 26 Sep 2010 at 12:02
I have download latest version Heekscad/cnc libarea libactp opencamlib compled
, but the error remain the versione libarea 62
Traceback (most recent call last):
File "/tmp/post.py", line 51, in <module>
c.append(area.Vertex(0, area.Point(69.999, 55.8), area.Point(70, 33.3)))
NameError: name 'c' is not defined
Original comment by b.ghiac...@gmail.com
on 26 Sep 2010 at 1:21
[deleted comment]
The pocket operation work with rectangular form rectangual-circle.heeks, but
when I create an pocket for a circle " with center and beam" that I transformed
in design I receive this error :
Traceback (most recent call last):
File "/tmp/post.py", line 52, in <module>
c.append(area.Vertex(0, area.Point(4.999, 41), area.Point(5, 19)))
NameError: name 'c' is not defined
Thanks.
Original comment by b.ghiac...@gmail.com
on 26 Sep 2010 at 1:31
The pocket operation work with rectangular form rectangual-circle.heeks, but
when I create an pocket for a circle " with center and beam" that I transformed
in design I receive this error :
python2.6: kbool/src/graph.cpp:236: void Graph::AddLink(Node*, Node*, int):
Assertion `begin && end' failed.
Thanks.
Original comment by b.ghiac...@gmail.com
on 26 Sep 2010 at 1:32
Attachments:
It's a known issue that you can't do machining operations to full circles with
HeeksCNC. The easy work around it so split the circle into 2 arcs.
Original comment by ddfalck2...@yahoo.com
on 26 Sep 2010 at 2:03
After some proves, I have got successful to make the pocket operation with
circle, I followed your's suggest, and I created two arcs after I transformed
it in a face, of course I generated the operation pocket on this.
HeeksCNC/CAD is, working very good.
Sorry, Luigi Barbati and me to ask your if is possible that , you create one
repositories svn public ( beta ) and one private ( alpha ) , that public repo
update not frequently but the some functions working very well, other repo (
alpha ) as current.
In this manner, the user choose the repo like him, that public with less
options but stable, or private with latest develop but not stable.
Of course, would have been very interesting for usability and good image for
you.
Thanks,
Palumbo Eugenio.
Original comment by b.ghiac...@gmail.com
on 27 Sep 2010 at 12:59
I think this got fixed.
Original comment by danhe...@gmail.com
on 24 Mar 2014 at 5:11
Original issue reported on code.google.com by
b.ghiac...@gmail.com
on 25 Sep 2010 at 10:09Attachments: