From: Guy K. K. <g....@ma...> - 2009-06-28 20:08:20
|
Hi Bruce, thanks for the explanations, I'll give it a try. I think whenever I set the visual.scene.visible = False my program stopped. It was a very strange behaviour. It was like there's still an event loop or so going from the GUI, and the only way to terminate the process was through an explicit kill. I need to have a look at it again. On Mon, 29 Jun 2009 03:59:02 Bruce Sherwood wrote: > I'm worried that something's apparently wrong with the del statement, > which should have gotten rid of the first display completely. I'll look > into that. Setting all the objects to invisible before making the > display invisible doesn't change anything. I've seen things like that before, wrapping native code in Python. I believe it's got more to do with the C side of things rather than the Python side. Python's del only acts on things that live in the Python world, and it does not/cannot call memory frees, destructors, etc. in the shared library's native code world. What I've done on ctypes based projects before was to add cleaning code to the Python object's __del__ method that performs some native code cleaning on deleting the Python object. Guy -- Guy K. Kloss Institute of Information and Mathematical Sciences Te Kura Pūtaiao o Mōhiohio me Pāngarau Massey University, Albany (North Shore City, Auckland) 473 State Highway 17, Gate 1, Mailroom, Quad B Building voice: +64 9 414-0800 ext. 9585 fax: +64 9 441-8181 G....@ma... http://www.massey.ac.nz/~gkloss |