2010/8/18 Free Cad <free...@ymail.com> > >Furthermore, what are the "python bugs added on top" you're talking about? > Is it > > > >the issues already reported here > http://code.google.com/p/pythonocc/issues/list > > >? I'm not sure they are the cause of your unsuccessful attempts. Did you > >identify other issues that have not been reported yet and I would not be > aware > >of? I'm much looking forward to having your feedbacks about it. >
Hi Björn, > > Of course, it would be better if all the problems shown in this list were > filed > as bug reports. But since the problems are always "investigated" or "looked > into", but never solved, I don't see the point in extending the list of > bugs. > If you don't have the manpower to fix problems, that's fair. But then say > so, > and people will get involved more deeply instead of abandoning pythonocc > with > bad feelings because after months their problem is still "investigated". > > I found that basically only the foundation classes module is more or less > well > supported by the python bindings. Especially the python bindings of the > modeling > data and modeling algorithms modules seem to be generated automatically > without > any unit tests ever applied. > Many thanks for letting us know your opinion. > > Maybe you can have a look at this one. Please don't tell me that you will > investigate the issue. If it can be solved within a week, I will reconsider > using pythonocc instead of C++, and I will take the time to submit bug > reports > for a bunch of other issues. An ultimatum? It's not usual in free software, especially outside of any commercial relationship. However, it's exciting to be challenged, even if I do not have any idea about who you are (but according to your message, it seems that it would be an honor for us that you use pythonocc). So first introduce yourself, your project and what you aim to bring to the project so that this challenge is a fair deal. > This example should create one wire from a sequence > of four edges. In C++ it works perfectly. Why does pythonocc create zero > wires > in ws? > > from OCC.BRepBuilderAPI import * > from OCC.gp import * > from OCC.TopTools import * > from OCC.TopoDS import * > from OCC.ShapeAnalysis import * > > vs=[[0,0,0],[1,0,0],[1,1,0],[0,1,0]]; > es=TopTools_HSequenceOfShape() > es.Append(BRepBuilderAPI_MakeEdge(gp_Pnt(*vs[0]),gp_Pnt(*vs[1])).Edge()) > es.Append(BRepBuilderAPI_MakeEdge(gp_Pnt(*vs[1]),gp_Pnt(*vs[2])).Edge()) > es.Append(BRepBuilderAPI_MakeEdge(gp_Pnt(*vs[2]),gp_Pnt(*vs[3])).Edge()) > es.Append(BRepBuilderAPI_MakeEdge(gp_Pnt(*vs[3]),gp_Pnt(*vs[0])).Edge()) > ws=TopTools_HSequenceOfShape() > safb=ShapeAnalysis_FreeBounds() > safb.ConnectEdgesToWires(es.GetHandle(),1e-3,False,ws.GetHandle()) > print ws.Length() > > Regards, > Björn > Best Regards, Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
