Blender Git Commits

Blender Git "master" branch commits.

Page: 4194 / 5574

November 11, 2010, 20:32 (GMT)
System console toggling for MinGW

Define WINVER=0x0501 for MinGW due to some stuff requres this winver, but
MinGW's default is 0x0400 (thanks AlexKu for point)

Better to replace all #include <windows.h> with #include "BLI_winstuff.h" to
avoid possibility of different functions prototypes in different modules.
November 11, 2010, 19:28 (GMT)
Fix for definitions checking. Now it should work with MinGW.
November 11, 2010, 19:04 (GMT)
Also !defined(FREE_WINDOWS) on appending operator.
Revision 5aa9d80 by gsr b3d
November 11, 2010, 19:00 (GMT)
SVN maintenance.
November 11, 2010, 18:53 (GMT)
== filebrowser ==
When loading .blend file (F1) open the filebrowser with the most recently used .blend file. Another lost feature from 2.49 back ;)
November 11, 2010, 18:24 (GMT)
wrong language :°
November 11, 2010, 18:21 (GMT)
For now have console toggling only when compiled with MSVC.
Need to find out how to enable for MingW too.
Revision c69bc46 by Janne Karhu
November 11, 2010, 17:59 (GMT)
Smoke now uses the start and end of cached data properly when outside the cached frame range.
* Patch by MiikaH.
Revision 1659e3f by Janne Karhu
November 11, 2010, 17:03 (GMT)
Bug fix: memoryleak when using smoke heat/velocity data as texture
* In addition to fixing the memleak it's much better to always copy the voxeldata to the texture. Smoke data can change at any time due to some changes, so we can't depend on that data.
* Thanks to MiikaH for finding this!
November 11, 2010, 16:50 (GMT)
Bugfix #20027

Texture Nodes didn't work for normal output anymore anymore.
It was caused by new handling of bump code using derivatives,
but that's not how texture nodes work now. In case a texture
has nodes, it uses the old (2.4) method.

November 11, 2010, 15:33 (GMT)
Bugfix #19534

Crash in Array Modifier. The merging-vertices option
(mysteriously named "First Last") caused invalid indices in
faces to exist. This commit solves the crash, but not the
cause. For that Ben Batt's assistance is needed.

November 11, 2010, 13:44 (GMT)
Apply patch [#24579] Fix for Win; Show/hide console
Submitted by Alexander Kuznetsov
November 11, 2010, 13:36 (GMT)
move report/operator view out of the 'Console' into the 'Info' space (file menu).

Ton will work on moving the File menu out of the Info space before release.

notes.
- reply Operator isn't working anymore.
- UI for reports is commented out so its not mixed with the file menu.
Revision c1a74d9 by Joshua Leung
November 11, 2010, 11:56 (GMT)
Animation Editors: Experimental indicators + "fixup" operator for "Disabled FCurves"

F-Curves tagged as "disabled" now have their channels drawn with a red line underlining their names.

"Disabled" F-Curves are skipped for evaluation, and typically result (for example) from assigning an action from one armature to another, but the new armature does not have some of the bones the action's F-Curves need in order for the datapaths (referring to the property the F-Curves affect) to be resolved. This is to prevent heaps of invalid channels slowing down animation playback.

I've also added a new operator, found by:
Channels -> Revive Disabled F-Curves
in the Graph Editor and DopeSheet/Action Editors, which will clear all the disabled tags for all the F-Curves in the animation editor at the time (based on the filtering criteria).

Use this operator to clear the disabled tags, allowing such channels to be able to be evaluated again (perhaps after adding the offending bones for example, or when using the action on the original armature again).
November 11, 2010, 11:53 (GMT)
Bugfix #24659

Material buttons: Wardiso slope button was not of type 'factor' (slider),
making it very hard to use.

November 11, 2010, 11:46 (GMT)
use BLI_snprintf, fixed building on msvc.
November 11, 2010, 11:06 (GMT)
Makefile fix: new compile flag moved to correct Makefile

November 11, 2010, 11:01 (GMT)
fix mistake in makefile
Revision 98e98bf by Joshua Leung
November 11, 2010, 10:27 (GMT)
Bugfix #24621: NLA strips move insensitively across tracks

This was a 2-part bug:
1) "Track index" (i.e. "index of NLA track within NLA Stack") was calculated incorrectly when the transform data is created. A typo meant that this was actually "index of strip within original track"

2) Strips were flying around madly vertically (especially for downward movements, and with extreme difficulty for upwards) as the track index was being updated incorrectly. I suspect at the time I was misreading it as trackIndex = ... vs trackIndex += ..., though it obviously looked wrong looking at it now!
Revision e3db157 by Joshua Leung
November 11, 2010, 10:07 (GMT)
NLA Transform Bugfix:

Transforming strips into locked tracks meant that they were not unlocked properly (i.e. they stayed as temporary "meta" strips). This is now taken into account as part of the step which checks if there's any space for them in those tracks.
By: Miika HämäläinenLast update: Nov-07-2014 14:18MiikaHweb | 2003-2021