[Bf-taskforce25] RNA-IPO

[Brecht Van Lommel]

Hi,

Joshua Leung wrote:
> What is unclear though, is what we should do with things like bones, 
> modifiers, and constraints.
> If we just used them in a straightforward way, as with the previous 
> examples:
> * for a modifier property - ob.modifiers["Subsurf"].render_levels
> * for a bone - ob.pose.bones["hand.R"].loc
> 
> However, the problem with this is that it's entirely possible to end up 
> mixing settings from objects, bones and constraints in the same 
> IPO-block. Thus, actions are effectively made quite redundant in such a 
> scenario, and you end up loosing benefits such as action-channel 
> grouping, unless some context wizardry is employed...

It does bring up this problem yes, what is the distinction between an 
Action and an IPO-block? Is it even useful to make a distinction? 
Maybe we don't need one, and an IPO block is just an Action that is 
owned by the ID block, and IPO blocks are redundant.

Brecht.