Revision 8e7ec36 by Lukas Toenne March 5, 2014, 16:44 (GMT) |
March 5, 2014, 16:31 (GMT) |
Alternative fix for T38753, use existing __file__ in namespace |
Revision 4f1a6eb by Campbell Barton March 5, 2014, 16:07 (GMT) |
Revision dd13bbc by Campbell Barton March 5, 2014, 15:40 (GMT) |
Previous linestyle icon was old patch, commit right one this time |
Revision 3aedb3a by Lukas Toenne March 5, 2014, 14:13 (GMT) |
Fix for invalid custom data checks in armature and lattice functions. Testing for custom data availability with getVertData and index 0 fails on assert for empty meshes (the index must be in valid range). Better use getVertDataArray which has no requirement for specific index. |
Revision df3116b by Campbell Barton March 5, 2014, 14:00 (GMT) |
Fix for un-subdivide creating duplicate faces |
Revision 26b1406 by Tamito Kajiyama March 5, 2014, 12:56 (GMT) |
Freestyle: Fix for incorrect comparisons of Nature values with integer and boolean values. The problem is that comparisons involving the constants Nature.POINT (for vertices) and Nature.NO_FEATURE (for edges) were evaluated in a wrong way. It is recalled that the Nature class is a subclass of Python's built-in int type, and that these two constants are zero when evaluated as numbers. The issue was caused by the implementation of the constants in an incompatible way for comparison with Python int (and boolean) values. Specifically, the zero of Python int is represented by an empty array of digits, whereas the zero-valued Nature constants were represented by an array of size 1. Python int comparison operators first check the lengths of the arrays of two operands, and then start comparing the digits only when the array length is the same. For this reason, the two Nature constants were not properly compared with int values (and thus with boolean values). It is noted that the zero-valued Nature constants may result from bitwise operations on other Nature constants (e.g., Nature.SILHOUETTE & Nature.BORDER), so this issue must have affected many existing style modules. The problem was reported by Folkert de Vries (flokkievids) through personal communications. Thanks a lot! |
Revision f5d2b46 by Campbell Barton March 5, 2014, 11:41 (GMT) |
Code cleanup: remove long unused gamma correction tables |
Revision e49e78e by Campbell Barton March 5, 2014, 11:41 (GMT) |
Fix for negative gamma correction rounding to int |
Revision c169413 by Lukas Toenne March 5, 2014, 09:01 (GMT) |
Fix for potential memory leak in Bullet API: freeing dynamic arrays should use the delete[] operator instead of the plain pointer delete. |
Revision a659d73 by Sergey Sharybin March 5, 2014, 08:52 (GMT) |
Added back code which was commented out for debug reasons Also added a patchset for Carve's memory leak fix. |
Revision 6ddb1fa by Sergey Sharybin March 5, 2014, 08:29 (GMT) |
Fix T38962: Boolean modifier crashes when only right operand has UV layer |
Revision 905dda8 by Sergey Sharybin March 5, 2014, 08:00 (GMT) |
Enable requests for buildbot and release builder |
Revision 4acff9d by jens verwiebe March 4, 2014, 20:08 (GMT) |
OSX/scons: according to last commit, , use the version variable |
Revision 40a2763 by Campbell Barton March 4, 2014, 19:45 (GMT) |
Edit to last commit, use the version veriable |
Revision 5d74cac by Campbell Barton March 4, 2014, 19:43 (GMT) |
Build system: option to copy 'requests' from scons. |
Revision ac7fba3 by jens verwiebe March 4, 2014, 19:31 (GMT) |
OSX/cmake: copy release/site-packages for OSX ( static py for now ) |
Revision 7cb8b6f by Campbell Barton March 4, 2014, 18:40 (GMT) |
Build system: add cmake option to install requests |
Revision 9ecf73f by Antonis Ryakiotakis March 4, 2014, 18:36 (GMT) |
Follow up to the offset scale fix for texture painting: texture mask had the same issue. |
Revision 976fd68 by jens verwiebe March 4, 2014, 17:41 (GMT) |
OSX/scons: copy release/site-packages for OSX ( static py for now ) |
|
|
|


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