Revision 84aa1dd by Campbell Barton March 6, 2013, 16:32 (GMT) |
fix for bug where array buttons would use -1 index, causing an out-of-bounds check on an array. added assert so this wont happen again. |
Revision fd399fa by Campbell Barton March 6, 2013, 15:38 (GMT) |
add asserts for passing negative index values to RNA functions which don't support them. |
Revision 74a9c15 by Campbell Barton March 6, 2013, 03:58 (GMT) |
Alternate fix for bug [#34369], where invalid polygon normals could be saved in the mesh data and in the file. This was from initial BMesh merge, but should not have been added in since face normals are calculated and stored in the DerivedMesh. Toggling editmode would remove poly-normals so its unlikely anything relies on this custom-data. |
Revision bf5eccc by Joshua Leung March 6, 2013, 03:53 (GMT) |
Woops! Fix for previous F-Curve path fix commit Trying to rename a valid F-Curve would crash as no RNA property was set, but *prop still had an uninitialised value. |
Revision 785c26a by Campbell Barton March 6, 2013, 02:57 (GMT) |
code cleanup: quiet warnings for recent weight paint theme addition. |
Revision 2827842 by Campbell Barton March 6, 2013, 02:52 (GMT) |
code cleanup: quiet float/double conversion warnings. |
Revision c270105 by Joshua Leung March 6, 2013, 01:59 (GMT) |
Bugfix [#32492] - Part 3: Error filter now includes drivers where there are errors with the variables/targets, even if those errors are for variables which aren't used (and are hence "harmless" errors) This means that the filter can be truly useful for helping locate things that need "cleaning up". For example, previously, there could still have been drivers where there were some of these "harmless" errors would emit warnings, but would otherwise appear perfectly functional. The implementation here uses a slightly slower method of checking any errors in these driver vars. However, it's no slower than what's done when these are evaluated, and should be less error prone than introducing yet another type of error tagging for this one case. The problem here is that the "driver invalid" flag, which is usually set when a target has errors, gets cleared by the pydrivers code if nothing went wrong when evaluating the expression. Removing this clearing step will probably open a can of worms, so unless this method proves to be far too slow, this simpler fix will do. |
Revision 8ebd5dd by Joshua Leung March 6, 2013, 01:44 (GMT) |
Experimental Feature: Ctrl-Click on the "name" of a broken F-Curve now allows you to fix the RNA Path in-place For F-Curves that are disabled or marked as having errors because their paths are invalid (indicated with a red line underneath their names), it is now possible to use the Ctrl-Click renaming functionality to bring up a textbox for fixing the offending RNA Path "in place" (i.e. in the channels list) without having to bring up the properties region first. This makes it easier to fix the paths if you know what you're doing. However, caution is still advised for most people. In particular, be aware that this uses a separate "RNA Array Index" for indexing into array properties (i.e. location, rotation, color) which will not be shown here, and can only be edited from the panel (or datablocks editor/scripts). |
Revision 11dbadb by Joshua Leung March 6, 2013, 00:56 (GMT) |
Feature Request: "Show Errors" Filter for Anim Editors now works for F-Curves/Animation as well as Drivers This is useful for tracking down invalid F-Curves which might need to have their paths fixed, or perhaps to remove F-Curves for controls which no longer exist in a new rig. |
Revision 0a83879 by Antonis Ryakiotakis March 5, 2013, 23:21 (GMT) |
The imperative per-few-days blenderplayer fix. |
Revision 15c524e by Daniel Genrich March 5, 2013, 22:58 (GMT) |
Bugfix [#34519] deleted cache after duplicating an object with baked simulation |
Revision f840ac9 by Gaia Clary March 5, 2013, 20:30 (GMT) |
Weight Painting: Added userpref for zero_weight color. |
Revision f5e1cde by Antonis Ryakiotakis March 5, 2013, 20:25 (GMT) |
Fix cursor display for anchored brushes due to own recent change of paint coordinate system. |
Revision dcbee8e by Bastien Montagne March 5, 2013, 15:15 (GMT) |
UI messages fix: no end point in tips! (from r55055). |
Revision f2bb536 by Campbell Barton March 5, 2013, 14:47 (GMT) |
code cleanup: also change BKE_blender.h BLENDER_VERSION_CHAR to 'a' so as not to confuse things. |
Revision 6537771 by Brecht Van Lommel March 5, 2013, 14:42 (GMT) |
Simple deform modifier: replace factor property by angle for twist and bend modes, so we can show degrees rather than radians. Still refers to the same DNA variable to keep backwards compatibility. Patch #33807 by Gottfried Hofmann. |
Revision a31c0bc by Sergey Sharybin March 5, 2013, 12:41 (GMT) |
View All operator for motion tracking dopesheet. |
Revision dab6f8f by Ton Roosendaal March 5, 2013, 11:19 (GMT) |
Bug fix #34534 Fix for 2.66a The new Copy/Paste objects feature could hang in eternal loop. Only happens for objects that refer to another scene via linkage. This fix then crashed Blender, needed to add a NULL check for screens. |
Revision f81b594 by Sergey Sharybin March 5, 2013, 09:38 (GMT) |
Switch from DENSE_NORMAL_CHOLESKY to DENSE_QR DENSE_QR is better behaved numerically and after recent changes from Sameer there's no big difference in speed. |
Revision 3a0d62f by Sergey Sharybin March 5, 2013, 09:38 (GMT) |
Update Ceres to 1.5RC3 It brings optimization of DENSE_QR and DENSE_SCHUR solvers. |
|
|
|


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