[Bf-committers] Auto-registration in Python

mindrones mindrones at gmail.com
Thu Oct 28 09:49:07 CEST 2010


Hi Nathan,

sometimes ago Barton Crouch wrote this one

http://wiki.blender.org/index.php/Dev:2.5/Py/API/Dynamic_Creation_of_Operators

Maybe it can be of some help?

Also, if you have some good finds about this topic, please consider 
adding to that page, thanks :)

Regards,
Luca

_____________________________

http://www.mindrones.com


On 10/28/2010 08:50 AM, Nathan Vegdahl wrote:
> After having worked on Rigify for a while, and also working on porting
> some custom scripts for Overgrowth, I'm really starting to despise the
> auto-registration of RNA properties, operators etc.
>
> I think this may be one of those things that is convenient in simple
> cases, but is just troublesome in complex cases.  For example, I'm
> still struggling to figure out how to make the Rigify addon unregister
> cleanly.  Ditto with the porting project I did.  It doesn't seem
> possible.  But it was trivial with manual registration.
>
> I would much rather manage the registration and un-registration
> manually, so I can guarantee that everything works cleanly even in
> weird corner-cases.
>
> And just as a 'feeling' the auto-registration seems too "magical" to
> me.  It's like my code is doing things I never told it to do.
> And it makes it difficult (impossible?), for example, to write a class
> (say, a panel) that is just meant to be inherited from, but not
> directly registered.
>
> Anyway, just my 2 cents.  I'm finding auto-registration to be a
> needless headache, for only minor convenience gains in simple cases.
>
> --Nathan
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers


More information about the Bf-committers mailing list