My first suggestion would be to keep the rendering in Python, if at
all feasible, and do only the actual simulation/computation in C.
Rasterizing a heightfield and rigid body plus some plash effects is
nothing that couldnt be done in PyOpenGL, or even something higher-
level like visvis or mayavi.
On Wed, Dec 21, 2011 at 2:10 PM, carlos choy wrote:
> Thank you for your great advice. It is detailed and tells me what I need
> to know, I wasn't expecting such an accurate response from anyone for some
> time.
>
> I think Option 2 is the way I will go. Having never embedded before, I
> think
I'd say go with option 1. Pass the window handler (or DC) to the rendered
thread.
To overcome the GIL problem, you can use Py_BEGIN_ALLOW_THREADS
(see http://docs.python.org/release/1.5.2/api/threads.html)
--
http://mail.python.org/mailman/listinfo/python-list
On Wed, Dec 21, 2011 at 11:19 AM, hbd666 wrote:
>
>
> In my experience implementing Option 1 in another project, I know that
> Python suspends
> execution until the DLL function calls return, but I did not launch the
> DLL on a thread.
> I expect that if the DLL were launched on a thread, a func
