2009/8/10 Sébastien Ramage <sebastien.ram...@gmail.com> > replace > > self.pnt.SetX(z[0]) >> by >> self.pnt.SetX(float(z[0])) >> >> >> - because it's an integer >> >> > Is it really a bug? I mean, do you have any segfault/traceback? Normally > pythonOCC handles integer/floats without any problem. For instance, > gp_Pnt(1,1,1) is the same as gp_Pnt(1.0,1.0,1.0). > > > yes you're right but the problem is numpy > > >>> import OCC.gp as gp > >>> import numpy > >>> a = gp.gp_Pnt() > >>> a.SetX(1) > >>> a.SetX(1.0) > >>> b = numpy.int32(10) > >>> a.SetX(b) > Traceback (most recent call last): > File "<interactive input>", line 1, in <module> > TypeError: in method 'gp_Pnt_SetX', argument 2 of type 'Standard_Real' > >>> >
Ok, right. > > >> >> test_gears_sympy.py >> python crash after creation of parameter DX2 saying access violation in >> TKMesh.dll >> don't know what that mean... > > > All these samples, as well as PAF, has been modified recently. It's not yet > been commited. > > ok so I will wait for. But this crash look like the problem that I resolved > by recompiling OCC with msvc9. > Can you provide the source for SalomeGeometry ? because I download it from > sourceforge but header files seems different from yours. > I compiled he latest svn rev. from the SalomeGeometry repository. The modified headers are only used to generate SWIG files. It's possible you need to recompile SalomeGeometry. > > > Sébastien > Thomas
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
