> I also tried the ctypes solution. It's almost impossible to achieve in a > 'blind' mode, i.e. without having the official documentation of the API > (impossible may be exaggerated, I mean I was not able to achieve it!). On the > other hand, this way to proceed is reverse engineering: if you ever manage to > be successful, the licence doesn't allow you to redistribute you work, and > you actually don't even have the right to do it.
For some time I worked a lot with Python & Rhino ( born "jungle boogie" ), which was a really decent way of programming Rhino. However, you hit some very _serious_ brick walls when diving a bit deeper; things such as topology traversal make life pretty miserable. What is so great about PythonOCC is how one can integrate basically anything, which is what the src/samples/Level2 examples point out in interesting ways. The dynamic simulation is an absolute attribute to this, _so_ excited to see this ported Thomas! -jelle _______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
