[Bf-python] Re: Modifier API

[Joe Eagar]

Ken Hughes wrote:
> In about two hours I made some reasonable progress; a 
> sequence/iterator to access all the Modifiers, and a wrapper which 
> lets you get/set the name of the modifier and check its type.  The 
> next step would be the mapping operations to get/set each modifier's 
> attributes.
>
> As to accessing modifier data when the user deletes it, if I 
> understand what you're asking, its the same issue we have elsewhere in 
> the API when there may be Python objects wrapping active data.  As 
> Stephen says, maintenance of object lifetimes is important (or 
> something to that effect).
>
> I can probably have something worth posting by the end of the weekend 
> (with documentation).  May not access all data for all modifier types, 
> but would be a first pass.  Or I can put up some ideas on the wiki and 
> people can kick the design around there.
>
> As for the generic listbase wrapper, I did start writing something 
> like this back in December, but it was for listbases and arrays.  I 
> think I came to the conclusion that there were (at this point) only a 
> few real places where this was useful, and the savings in space were 
> not substantial.  Of course, when Blender 3.0 is rewritten in python, 
> will all be moot anyway :-)
>
> Ken
Don't let intrr hear that :)

joeedh