January 25, 2010, 07:19 (GMT) |
Added a 'linked' icon to modal key maps, to communicate better that they're instantiated. Helps [#20778] [2.5 - r26180] "Gesture Border" items in user preferences panel are not unique |
January 25, 2010, 07:05 (GMT) |
Fix for bug in drivers, introduced in previous commit. |
January 25, 2010, 06:48 (GMT) |
Fix [#20786] Added widget on toolbar does not remove Fix [#20794] Can't save my file by pressing "Enter" button - removed the ability to activate a text field by pressing enter when the mouse is over it. This wasn't that practical and now allows the convenient 2.4 behaviour in the file selector filename field, of pressing enter twice to save. |
January 25, 2010, 06:24 (GMT) |
Radians -> Degrees (in UI) Rotations are now stored internally as radians, while exposing degrees in the UI - in the graph editor and UI controls. This is done in two areas: 1) Using the unit system to convert RNA data to display as degrees in the UI controls 2) FCurves now use degrees for rotation, so you can edit in the graph editor what you see in the UI. All rotation data is consistently accessible in DNA and RNA as radians, degrees are only used for the UI controls and graph editor. This commit includes conversions will convert old files (stored data and also fcurve data) to the new units, hopefully everything should go smoothly! Part of this also changes a few properties that were hard-coded as degrees before (such as IK pole angle and brush texture rotation) to also use the same consistent system of radians (dna/rna) and degrees (ui). Thanks to Joshua for hints and review here too. |
Revision c94f385 by Joshua Leung January 24, 2010, 23:18 (GMT) |
Bugfix #20806: Remove button removes entire bone group not bone from group Thanks to kristijonas vaicekauskas (krizas) for the patch |
Revision 3c09bd4 by Tamito Kajiyama January 24, 2010, 23:12 (GMT) |
Clipping of imported meshes by the near and far view planes. A straightforward clipping algorithm was implemented to eliminate vertices that are out of the interval from the near to far clipping distance defined by the active camera. Previously, objects that come behind the camera could lead to a crash. The changes in this commit is intended to address this issue. When meshes are partially clipped, new edges are added. These edges can result in visible strokes if they are within the camera view. |
Revision 1deecdb by Joshua Leung January 24, 2010, 23:08 (GMT) |
Bugfix #20782: Animating two materials on a mesh--only first material's keyframes show up in f-curves editor Wrong indices were being used to reference materials, resulting in too few materials showing up. It seems that at some point since coding this in the 2.4 codebase and now, the range has changed from [0, totcol) to [1, totcol]. |
Revision 265b934 by Elia Sarti January 24, 2010, 19:30 (GMT) |
Forgot to rename use_return in this script as well. |
Revision 8923ba9 by Campbell Barton January 24, 2010, 17:40 (GMT) |
unlinking objects from a scene in python wasnt notifying the outliner which would crash on redraw. |
Revision 120c72e by Campbell Barton January 24, 2010, 13:11 (GMT) |
remove deprecated functions |
Revision 7389bd5 by Benoit Bolsee January 24, 2010, 13:03 (GMT) |
Update MSVC project files |
Revision 2cfd3b6 by Campbell Barton January 24, 2010, 12:58 (GMT) |
copy of docs from 2.4x for python modules that have been kept |
Revision 0fadd50 by Elia Sarti January 24, 2010, 11:02 (GMT) |
Forgot this (rename use_return to use_output) |
Revision 9733e90 by Elia Sarti January 24, 2010, 10:51 (GMT) |
RNA functions Fixed and completed support for returning multiple values. This includes support for returning arrays, both fixed and dynamically sized. The way this is achieved is by storing an additional int value next to the dynamic parameter in the ParameterList stack which gets passed to the C function as an additional parameter. In the case of return parameters it is duty of the C function to set this int to the correct length value for the dynamic parameter (which makes sense). Note that for the dynamic output/return parameter it is assumed the function has allocated that memory (which gets freed automatically). Also, I cleaned the makesrna's bridge function generation code a bit and renamed PROP_RETURN to PROP_OUTPUT, which represents better the reality now that there are multiple returns. The function now to mark multiple returns (outputs) is RNA_def_function_output. For an example, look at Action.get_frame_range in rna_action_api.c, by the way Aligorith I removed the #ifdef for this function now that there's support for returning arrays, feel free to modify (the function seems to work). |
Revision 7c21eb7 by Joshua Leung January 24, 2010, 10:18 (GMT) |
Bugfix #20664: NLA Editor - Hiding stuff causes instant crash .. |
Revision b4640bf by Joshua Leung January 24, 2010, 09:58 (GMT) |
Bugfix #20776: Segfault Driving a Shapekey in Graph Editor > Drivers > Selecting the Bone ID-Type for Driver Targets should sometimes not be editable, otherwise, users could set invalid datablocks, leading to crashes. Added missing checks for this to prevent this happening again. |
Revision ac38eba by Joshua Leung January 24, 2010, 06:28 (GMT) |
NLA Editor: Sync Action Extents with Referenced Range This operator can be accessed from the "Action Clip" panel, and is used to include keyframes that have been added to a strip already in the NLA. Although this is not a recommended workflow, having this ability is useful at times. |
Revision 351d239 by Joseph Eagar January 24, 2010, 04:26 (GMT) |
View3d transform was sending a too-general notifier to redraw, causing several animation editors and the property editor to redraw too, which can really slow things down. added a more specific ND_VIEW3D_TRANSFORM notifier to solve this. |
Revision 27db00b by Joseph Eagar January 24, 2010, 02:59 (GMT) |
remove own experiemental code |
Revision 22f7c8b by Campbell Barton January 23, 2010, 20:43 (GMT) |
support for compiling blender without python working again (with cmake at least) |
|