Blender Git Commits

fix [#26545] Crash when changing values for properties after changing max-min

tried doing this smarter by validating the property exists in UI code before access but this ended up making it too complicated and also hard to account for possible access without checking every time.

for now just redraw all areas when a user property is changed.

write project files into the build dir.

fix for incorrect array use when freeing fcurve modifier envelope points, array also wasnt NULL'd on freeing which gave memory errors later on.

ZanQdo Bugfix:

Envelope FModifier data points were getting saved in a non-portable
way. Apparently this broke when trying to read files with this data on
PPC machines if the files were saved using Intel machines.

RNA & interface functions for checking if RNA in a button uses valid rna property (not currently used).

the script is now creating 2 project files:

Blender.creator
Blender_Python.creator

.glsl files have been added to the former
latter contains everything .py

tag variable as unused.

Pose Menu Tweak: Moved keyframe management items into sub-menu like in
Object menu

Reshuffled utility function to keyframe drawing API, removing some
duplicate code

Animation Tool: Propagate Pose

This tool automates the process of copying a pose to successive
keyframes, making it easier for animators to go back and change the
pose for some controls which remain "static" for periods of time.
Previously, animators would need to do a "{Ctrl-Pageup Ctrl-V} *
number_of_static_keyframes" dance for each set of controls that this
happened on, which is not too good ergonomically speaking.

There are two modes exposed via the menu (Pose->Propagate):
- "Pose Propagate" - also known as the 'WHILE_HELD' mode, which
propagates to all keyframes that are holding the same value
- "To Next Keyframe" - which only propagates the pose to the closest
keyframe in the occurring after (but not including) the current frame

Additionally, there are a few other modes that can be used, though
they are less useful for direct use from the UI, though they can be
used via the PyAPI as need be.

---

Also, I did some cleanups in the "Pose" menu to bring it more into
line with the Object mode one. There are some more tweaks that could
still be done here, such as bringing the keyframing operator entries
under a submenu too (as in the Object mode version) to get the length
of this under control.

support for blender as a module on win32.

Fix #26571: slow approximate AO with zero area faces.

fix [#26591] File browser: select multiple files for Library append/link broken
* added check for valid files a bit too eagerly in Rev.35654. Solved now by
setting correct type for .blend file contents. Objects are now tagged as
regular files, while the list (Mesh, Material, ...) (no idcode given) is
tagged as directory.

IRC bugreport:

Splitting/joining editors (areas) was possible in full-screen mode.
That's not possible, crashes on going back to previous.

fix [#26456] weightpaint mode with armature modifier, armature mode
disable bone selection in weightpaint mode when the armature is not in pose mode.

Additonal fix for r35724

(bugfix #26573, #26574 and #26551)

Layer visibility code for hotkeys uses different code still, added same
new DAG_on_visible_update() in this operator.

missed committing this before

fix for building collada on linux

COLLADA: supporting barebone class for <extra> support (incomplete).

fix [#26588] In render view, Blender crashes when collapsing an opened split render pane if you have the histogram tab open in the pane your collapsing.