Revision 3b3d811 by Sergey Sharybin February 2, 2012, 19:20 (GMT) |
Disallow fill caps for curves without bevel object. It's getting complicated to detect which part of curve is actually a cap in cases like extruded 2d curve with non-zero depth. |
Revision 1471a19 by Sergey Sharybin February 2, 2012, 18:50 (GMT) |
Fix for recent bevel cap option "Holes" used to be ignored (i.e. when using "Text" as bevel object "e" wouldn't have a "hole"). Resolved by collecting all polys needed for top and bottom cap and filling them at once |
Revision aef11b5 by Sergey Sharybin February 2, 2012, 15:15 (GMT) |
Added option to fill caps of bevelled curves. It can be found in Shape panel below Fill label. If this option is enabled, caps of curve will be filled. |
Revision 4aaf593 by Brecht Van Lommel February 2, 2012, 14:07 (GMT) |
Fix #27213: editing color ramp "Pos:" number value did not update the ramp properly, when moving the current point before another. |
Revision 8f01ad9 by Brecht Van Lommel February 2, 2012, 13:35 (GMT) |
Fix #29056: keymapping NDOF motion events not working correct. Motion even type was missing in python. |
Revision 01d0e27 by Brecht Van Lommel February 2, 2012, 13:21 (GMT) |
Fix related to #30053: crash rendering scene strips without a scene (due to missing library). |
Revision 3719942 by Sergey Sharybin February 2, 2012, 13:04 (GMT) |
Revision 4515578 by Campbell Barton February 2, 2012, 11:12 (GMT) |
own attempted simplification to previous patch was incorrect. |
Revision 2c5d936 by Campbell Barton February 2, 2012, 11:08 (GMT) |
patch from Peter Stern to fix CMake building on OSX (without manual editing of configuration) |
Revision 5d6527d by Domino Marama February 2, 2012, 10:34 (GMT) |
Patch #29705: Collada export didn't export mesh name. Added name= parameter to geometry nodes in Collada export |
Revision 6a30321 by Sergey Sharybin February 2, 2012, 08:48 (GMT) |
Fix #29381: Navmeshs frees not guarded allocated memory and leaked There were two issues discovered: - Triangles mapping didn't free in buildNavMeshData if there's no recast data for an object - KX_NavMeshObject used not-guarded allocation for polygons storage, but used guarded freeing stuff to free used memory, producing error messages in the console and leading to memory leak. Wasn't actually harmful for users -- there was no memory corruptions and error happens only when object was set up in a way when navmesh can't work in theory. |
Revision 722e0d3 by Campbell Barton February 2, 2012, 08:47 (GMT) |
Code Cleanup: de-duplicate bone space calculation ~(35 sloc) |
Revision ab4dbc6 by Campbell Barton February 2, 2012, 08:04 (GMT) |
fix [#30051] Copy Scale constraint overrides Inherit Scale from parent space conversion in constraint code ignored inherit scale option. |
Revision 38ad71f by Campbell Barton February 2, 2012, 07:37 (GMT) |
Cleanup Only: replace numbers with defines. |
Revision dd86ae6 by Campbell Barton February 2, 2012, 05:55 (GMT) |
fix [#28296] File selector crash when with filepath property disable browsing a file property within the file selector to avoid a crash. |
Revision d8c4e59 by Campbell Barton February 2, 2012, 05:11 (GMT) |
* fix for error in shape transfer (wrong var name). * fix for error alligning object to the view when no space was set. also added blenderplayer start to CTest operator blacklist. |
Revision 369ae3d by Campbell Barton February 2, 2012, 04:59 (GMT) |
internal cleanup, check. * remove duplicate operator, wasnt used. * added check for duplicate types for CTest. |
Revision 697e77a by Campbell Barton February 2, 2012, 04:43 (GMT) |
fix [#29666] Duplicate entries in bpy.types Python operator subclasses and operator types each get their own SRNA, causing double ups for bpy.types.__dir__() From the operator type - these share names. * ot->ext.srna * ot->srna Note that this conflict is still there, this only disables 'ot->ext.srna' from being included in dir(bpy.types). |
Revision 5a221dd by Andrew Hale February 2, 2012, 01:07 (GMT) |
Fix for possible memory leak on creation of a vector using Vector.Range. It was possible to allocate an array of size<2 which would then raise an error on vector creation without freeing. Fix to ensure the behaviour of Vector.Range was the same as for builtin range() function. When specifying 3 arguments, the step argument wasn't being used to correctly calculate the vector size. Minor formatting edits for error messages. |
Revision 8926cbd by Campbell Barton February 2, 2012, 00:04 (GMT) |
svn merge ^/trunk/blender -r43819:43830 |
|
|
|


Master Commits
MiikaH:n Sivut a.k.a. MiikaHweb | 2003-2021