these calls were done without anything actually happening, for each
mouse move, and caused quite some slowdown at OSX.
Might help the other platforms as well. Check it by just moving your mouse
around, over window edges, buttons, etc. Especially Radiosity buttons
were horrible slow in a large window
Please be aware that the above calls cause a swapbuffer at OSX!
so extended it so Simon's redefinition also occurs whenever
FP_INFINITE isn't defined (don't know why setting infinity
equals to 1 would be a good thing though)... maybe the author
might choose a more portable method for doing this.
A quick HOW-TO:
* Open /blender/projectfiles/blender/blender.dsw
* Replace all existing files in the exppython project with the
.c/h files found in /blender/source/blender/python/ and subdirs
* Make sure Blender project is active.
* Remove the old BPY_python and BPY_freeze dependancies.
(Project->Dependancies...)
* Add the new exppython as a dependancy.
* Recompile, et voila! :)
I'm sure the python team would appreciate some Windows feedback,
so please test this if you can and report any probs, etc to the
bf-python mailist.
Note: The old BPY_python/freeze project will be removed and exppython
made default just as soon as it is declared ready! ;)
--aphex
eat up cpu time.
in fact it was in pre-ghost blender already.
works now for all posix OS's, except for windows. now working on getting
that fixed as well. until then, rendering will be slow at win32...
cvS: ----------------------------------------------------------------------
Now Blender.NMesh.PutRaw() doesn't destroy vertex color info anymore.
Both exppython's NMesh.c and bpython's opy_nmesh.c were updated.
* Minor changes in other files.
confusing functions which were only used once.
Part of examining how renderwindows get opened/closed, and to enable
a third option for render output to ImageWindow in Blender
- Trying to fix linking problems in OSX;
- Making module .Get functions behave like the ones in Blender 2.25 - 2.27
(Guignot pointed the incompatibility);
- Included more types to Blender.Types;
- Found by luck and corrected two bugs that were making Blender crash;
- Added/updated some simple functions.
When a script that used setAttr for Camera Data objs (the bug also
affected some other modules) was executed multiple times, Blender
would crash after, let's say, the first 5 or 6 tries. Problem, as
Guignot pointed, was with reference counting. Should be ok now, all
affected modules were fixed.
* The Scene module is now "complete" (= 2.25).
* Made some necessary updates to Object and NMesh.
guignot
Ton Roosendaal
Willian Padovani Germano
Casey Corn
Michel Selten
Stefan Gartner
Simon Clitherow
Kent Mein
Rob Haarsma