Blender Git Commits

Fix CMake build system for Windows
Add support for OPTION WITH_OPENCOLLADA for Windows

New function:

void MEM_callbackmemlist(void (*func)(void*));

Will call the function passed as argument with all allocated address as parameter. Useful for debuging.

Math Lib

* Post-conversion commit, fixing some introduced warnings.

Split operator internal call (for python) between invoke and exec. Only invoke needs window (for event), no need to require it for exec too.

No functionality changes, except that operator called with exec when a window isn't present (say, bg mode) won't silently fail.

Math Lib

* Convert all code to use new functions.
* Branch maintainers may want to skip this commit, and run this
conversion script instead, if they use a lot of math functions
in new code:
http://www.pasteall.org/9052/python

Math Lib

* Pre-conversion commit removing old arithb.c code, this will not compile,
next commit fixes that.

NULL pointer check to prevent some crash in background mode

Running with -d, python context also prints members asked from context that are present.

Also, error messages were mixed up, wrong type and not present where inversed.

Add Sticky was essentially a blank operator. Possibly context functions weren't around for this one when it was first looked at. Re-attached so it works now.

SVN maintenance.

Math Lib

* Fix remaining issues before conversion.
* Inline various vector functions, currently enabled for all platforms.
I expect this to work in GCC/MSVC at least, if other platforms don't
support it, #ifdef's can be added.

Function declaration for BPY_context_get

fix error with python exceptions in BPy_errors_to_report

2.4x fix for Blender.Load()
only bother checking script spaces when loading a blend file

Should be able to load a STL or DXF when script spaces are open now

modify the python context access so invalid names will raise an exception rather then returning None.
this way the UI scripts are less likely to fail silently and wont let typos work ok.

also allow subclassing of the context, added a copy function,
bpy.context.copy(), returns the context as a python dict to be modified and used in python.

This also showed up an invalid brush member in the screen context.

fix for own error in active bone commit, wasnt checking object type was an armature
also fix for warning with printf

Drag & drop implementation at GHOST level (only OSX for now)

The dragging sequence is performed in four phases:

- Start sequence (GHOST_kEventDraggingEntered) that tells a drag'n'drop operation has started. Already gives the object data type, and the entering mouse location

- Update mouse position (GHOST_kEventDraggingUpdated) sent upon each mouse move until the drag'n'drop operation stops, to give the updated mouse position.
Useful to highlight a potential destination, and update the status (through GHOST_setAcceptDragOperation) telling if the object can be dropped at the current cursor position.

- Abort drag'n'drop sequence (GHOST_kEventDraggingExited) sent when the user moved the mouse outside the window.

- Send the dropped data (GHOST_kEventDraggingDropDone)

- Outside of the normal sequence, dropped data can be sent (GHOST_kEventDraggingDropOnIcon). This can happen when the user drops an object on the application icon. (Also used in OSX to pass the filename of the document the user doubled-clicked in the finder)

Note that the event handler is responsible for freeing the received data.
And the mouse position is sent directly in blender client coordinates (y=0 at bottom)

The GHOST_setAcceptDragOperation(TRUE) call must be placed before the user drops the object for it to be accepted.

Current handled data types :
- Text string
- Array of filenames (full paths)
- Bitmap image (not implemented yet)

merged changes to revision 24446

Fix for math lib commit, had duplicate definitions of functions,
giving build issues on some platforms.

Bugfix #19835: While playing animation, Render>Dimensions>FrameRate does not change animation speed

The timestep used for the playback timer now gets adjusted accordingly when the frames-per-second setting gets changed during playback (i.e. in the "animation_step" operator). This is not as ideal as only updating this when the framerate setting is changed, but using an appropriate update function for this failed miserably.