Blender Git Commits

one small change -- SpaceNav works on Windows

SpaceNav works on Linux

BGE Animations: KX_GameObjects now only instantiate a BL_ActionManger if they need one.

Merged changes in the trunk up to revision 37388.

Conflicts resolved:
release/scripts/startup/bl_ui/properties_render.py
source/creator/SConscript
source/blender/blenlib/intern/bpath.c
source/blender/editors/space_outliner/outliner.c

BGE Animations:
* Adding BL_Action::Play() and BL_Action::Stop()
* Making BL_ActonManger reuse BL_Actions instead of recreating them all the time
* Making the Property play type work for the Action actuator.

* Code cleanup

suspiciously consistent typo

2.5 Modifier UI Script:
* Tiny improvement, no need to have split declaration outside of if branch.

Fixed Multi-Paint so that it doesn't stop painting unless the maximum cap has been met.
Also, the color display now only shows colors for the areas that are shared by the selected groups.
Finally, Multi-Paint responds to auto normalize, it determines when it can not be edited.

Camera tracking integration
===========================

Fixes for windows compilation

Cycles: button to switch to texture tab from e.g. modifiers and field, with the
relevant texture selected, and some cosmetic tweaks to the menu.

Camera tracking integration
===========================

- Added missed stub for blenderplayer, so it should
compile again fine.
- libmv is added to extern/.
Script for bundling needed subset of sourcses from
libmv repo is included there.
- Eigen3 is also added to extern/.
libmv depends on Eigen3 (which isnt't compatible with Eigen2
from API point of view). So both of versions are going to
be in worktree for time (until code which used Eigen2 would be
ported to Eigen3).
- Added some functions to libmv-capi, so some things from
this library could already be used.
- Added the very basic implementation of 2D tracking.
It should be treated as draft for tracking architecture
which probably would be cleaned up, changed or whatever else.
Current implementation was supposed to demonstrate that our
structures and understading is correct to interact with libmv easily.

Camera tracking integration
===========================

- Disallow moving pattern/search area in way when marker position is
outside of pattern area.
- MoiveClip could be set as background for 3D view.
Added background source property to BGPic to switch between image
and movie. Movie is a bit more complicaated entity than clip (due to
displaying bundles, test objects and so) that's why i've sliptted
background into two sources.
- Added Layout.template_movieclip to display general clip settings.
Used in Footage panel of SpaceClip and background image properties
in 3d view.
- Display bundles in 3D view as spheres. Selection is synchronized to
markers associated with this bundle.
Bundle can't be selected in 3D view.
- Recoded internal DNA structures, RNA and operators to match libmv entities.
Tracking data now consists of Tracks, each tracks consists of markers
which are associated with frame number. Markers holds position only,
pattern and search areas settings are stored in track. Such settings should
be unified for all markers in track and marker should hold position and
frame number only.

fix [#27627] Strange behavior with solid open gl lights
disable turning off all lights in the user preferences.

Merging r37123 through r37370 from trunk into soc-2011-tomato:

Cycles: GLSL error fix for image and environment nodes with no datablock assigned.

Bugfix #27136

Ending localview - which is similar to layer change - should send
update similar to change layers too. Needed for example when loading
a file saved in local view or when changing time in localview.

Cycles: quick GLSL stubs for new material nodes, so they show something.

BSDFs and procedural textures show mostly as diffuse and white, geometry
and texture coordinates are incomplete.

Alignment tweaks to F-Modifier header buttons.

I was going to include this change along with support for moving
FModifiers around on the stack, though that looks like it might be a
bit more involved than first though. To be dealt with later...

Adding properties to Keying Sets via the Scene properties will now set
"entire array" property on by default, making it easier to add
transforms to Keying Sets.

This doesn't affect Keying Set paths added via Python or any other
means.