[Bf-committers] Make Parent - shouldn't it work differently?

[Bassam Kurdali]

What i would like to see here is stack based (modo) or nodal (maya) transforms- that way you could:

expose inverse parent transform
get rid of hard coded dx dy dz transforms
expose constraint offset transforms, and simplify constraints
expose child of constraint
freeze transforms ala maya by popping a transform onto stack
stack as many offsets as you need for rigging
get rid of hard coded transform/constraint order of evaluation
get rid of confusion that hidden transforms cause
make all hidden transforms editable

some of the benefits I list assume of course that constraints and perhaps parenting are also in the stack/node tree. Most of the previous list is not currently possible.

As for the current behaviour, if you:
ctrl p
then
ctrl alt p - clear inverse parent
i believe you'll have what you want. Not sure if there is an operator that just does that (though editing the parent property in the properties editor does. Does it have copy to selected? )

the default behaviour should be kept, of course. Most users want this.

On Fri Sep 21 2012 05:08:08 AM EDT, Remigiusz Fiedler <migius at gmx.net> wrote:

> oops, haven't read your post to the end
> 
> > There is of-course the option to parent objects using Shift-Ctl-P.
> > This creates proper relation between "A"'s transform properties and
> > its visual transformations, but it as well moves "A" to "B"'s location
> > and it's not always the desired result.
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers