[Bf-taskforce25] Wrapping pose channel vs. bone flags and other stuff

[Joshua Leung]

Hi Roland,

I was just having a look through the RNA wrapping for PoseChannels, and it
looks like you've left out the most important bits, and exposed stuff you
shouldn't have.

Important things missing
* loc/rot(quat)/scale settings have not been exposed yet. These are the
user-editable transform settings used to pose armatures. The new animation
system will definitely need this...
* bone group setting - I'll probably fix this myself...

Incorrectly exposed things
* 'protected' setting - this is really the transform locks stuff PER CHANNEL
(locx/locy/loc/rotx/roty/rotz/scalex/scaley/scalez) instead of a single
boolean. Check how this is done for objects, since it uses the same flags.
* pose head/tail location - these are set internally and shouldn't be
editable by the user. Personally, I'd prefer if they were not exposed at
all, but that is debatable. Same goes for the matrices...

Weird things
* 'parent' entry seems to be duplicated here for some reason... Perhaps it's
just an old build I'm running.

Regards,
Joshua


On Tue, Jan 6, 2009 at 7:09 AM, Roland Hess <me at harkyman.com> wrote:

> Joshua -- saw your note in the armature/bone rna about whether to wrap
> the bone or pose channel version of that data. My vote would be to keep
> it in bone, and for the most part leave pose channel unwrapped.
> Re-looking at the two, there isn't as much overlap as I remember.
>
> I'd suggest: wrap for read-write (when appropriate) in Bone, and also
> wrap in Pose channel but read only, and a note in the doc string that
> it's a bone-level flag.
>
> Roland
> harkyman
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-taskforce25/attachments/20090116/ae9252d3/attachment.htm