Revision f09a361 by Joseph Gilbert November 7, 2005, 20:03 (GMT) |
*armature api for python - don't get too excited - allows you to get armatures from a scene - makeEditable()/saveChanges() puts the armature into out of editmode (pythonically) - Armature.bones is a dictionary that contains all the bones in the armature and can be iterated - getters are available for: name, roll (dictionary) keys are BONESPACE, ARMATURESPACE head (dictionary) keys are BONESPACE, ARMATURESPACE tail (dictionary) keys are BONESPACE, ARMATURESPACE matrix (dictionary) keys are BONESPACE, ARMATURESPACE weight deform_dist subdivisions options (list of constants) parent children Setter work only in editmode. Some are not fully implemented. Type class is embedded in the module. This means the construct is called as follows: Blender.Armature.ArmatureType() import Blender.Armature as Armature arm = Armature.Get('myarm') for name, bone in arm.bones.items(): ...print name, bone, bone.matrix['ARMATURESPACE'] more documentation is forth coming. This is an alpha for this api. |
Revision a39559e by Joseph Gilbert November 7, 2005, 19:36 (GMT) |
*change to the way constants are printed |
Revision cce655b by Joseph Gilbert November 7, 2005, 19:34 (GMT) |
- warning fixes * various warnings the python api is putting out |
Revision f7c955b by Alexander Ewering November 7, 2005, 13:22 (GMT) |
First part of sequencer attack: Sequencer image preview finally supports zooming out. Yay! |
Revision 979c28b by Ken Hughes November 7, 2005, 00:22 (GMT) |
-- Clean-up of Effect and Particle modules; since particle was the only remaining effect type, it didn't make much sense to leave things implemented in two separate files. Changes include: * two bug fixes (the getChild() and getMat() methods were using floats instead of shorts) * performing clamping on input values * implementing attributes using tp_getset * merging Effect and Particle functions: the Particle module exists in name only, with the Particle.New() and Particle.Get() functions remaining for backward compatibility (they are in fact identical to Effect.New() and Effect.Get() functions) * update of doc/Effect.py (including remove all old references to wave and build effects) |
Revision 0089c0b by Ken Hughes November 6, 2005, 22:29 (GMT) |
-- Added Object.effects, a read-only attribute which returns a list of the particle effects belonging to an object (based on patch from jms) |
Revision 25dc335 by Ton Roosendaal November 6, 2005, 19:02 (GMT) |
Bugfix #3358 Deleting a shape key object could crash, when ipowindow open and showing an active key. Also: patch from tracker to increase limits of buttons for background image offset. |
Revision dfce9d7 by Erwin Coumans November 6, 2005, 16:50 (GMT) |
minor cleanup. Todo: Does 'testhandles' need to be called after every single ipo_insert_vert ? |
Revision d1be55f by Andrea Weikert November 6, 2005, 16:32 (GMT) |
Small fix to allow relative filenames for textfiles. |
Revision 0fbd27f by Chris Want November 5, 2005, 22:20 (GMT) |
I seem to have problems with the distinction between else and #else today. My apologies! |
Revision 58ef9fb by Ton Roosendaal November 5, 2005, 21:51 (GMT) |
Modifier fix; new Armature modifier added sets the deform flags on. (Note; until 2.40 release, these flags are also still in the Armature Panel, that will disappear then) |
Revision 8b8daec by Ton Roosendaal November 5, 2005, 21:40 (GMT) |
Another typo in ALT+C convert modifiers; it was copying data from the wrong object, which worked until a few days ago when I fixed a bug in add_object(). :) |
Revision ebfd6de by Ton Roosendaal November 5, 2005, 21:17 (GMT) |
Bugfix #3249 Error in BLI_array_randomize(), an unused call in Blender until the Build Modifier was added. It did a weird modulus I don't really grasp... somehow that caused the bug (create a corrupt mesh). But why? Dunno... |
Revision 165ed1b by Chris Want November 5, 2005, 21:09 (GMT) |
Use limits.h and float.h on *bsd instead of values.h. On this subject (and thanks to GSR for research) on debian the values.h has the following warning: /* This interface is obsolete. New programs should use <limits.h> and/or <float.h> instead of <values.h>. */ Should values.h be used at all? |
Revision ffdde59 by Ton Roosendaal November 5, 2005, 20:02 (GMT) |
Bugfix #3342 Target-less IK, with a hinge bone that has an offset to its parent, didn't get applied correctly after transform. |
November 5, 2005, 18:40 (GMT) |
* 3D View menus updates. mainly just adding missing functionality that only had hotkey access before and tweaking organisation of new stuff. |
Revision bb14718 by Ton Roosendaal November 5, 2005, 18:23 (GMT) |
Bugfix #3237 Selecting Edges in "Cut Away View" (ALT+B) did not work yet for wire view. Solved it by calculating the closest coordinate for mouse to edge, and check for that position if it's visible or not. |
November 5, 2005, 17:19 (GMT) |
I think I committed something I shouldn't have. Hopefully this will fix compilation. |
Revision 1d85275 by Ton Roosendaal November 5, 2005, 17:14 (GMT) |
Fix #3256 DXF: when an error message occurs during read, the main call returned without clearing the used global vars... causing crash on calling again. ALso: added warning when trying to assign a taper or bevel using Object itself. (report from opengl tracker :) |
November 5, 2005, 16:35 (GMT) |
* Buttons window tab cycling Repeated presses of the F* key to go to a buttons context will now cycle through the sub-tabs within. For example, when at a different buttons window context, pressing F7 twice will cycle through to the Physics buttons tab, pressing F10 three times will cycle through to the Sound buttons tab, etc. |
|
|
|


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