HEY!!
How about letting addon developers know how this new opt-in implementation
is supposed to work before ploughing ahead and seriously breaking
everything, again.
I'm not arguing here about whether this is better or not - but as it stands
now I've no idea now how to initalise my addon !
Yours
ta/svn/bf-blender [34765] trunk/blender/release/scripts: patch [#25809]
> Auto-Registration as utility function.
> To: bf-committers@blender.org
> Received: Thursday, February 10, 2011, 7:09 PM
> HEY!!
>
> How about letting addon developers know how this new opt-in
> implemen
Hi Doug, I should have been more clear that I'll be updating addons next.
In most cases 'bpy.utils.register_module' /
'bpy.utils.unregister_module' just need adding.
example from OBJ i/o (menu registration functions we're already there).
def register():
bpy.utils.register_module(__name__)
Doug, just finished getting addons working again without auto
register. (not contrib yet).
But heres an overview of the changes I needed to make.
- bpy.utils.(un)register_module(__name__) as described above is good
enough for most addons, this is equivalent to what auto-register was
doing before.
Campbell,
Maybe something about this should be posted on code.blender.org so that more
people know about the change.
Cheers,
Jonathan
___
Bf-committers mailing list
Bf-committers@blender.org
http://lists.blender.org/mailman/listinfo/bf-committers
Also, what about the bf-python ML ?
Cheers,
Doug.
On 11 February 2011 12:19, Jonathan Smith wrote:
> Campbell,
>
> Maybe something about this should be posted on code.blender.org so that
> more
> people know about the change.
>
> Cheers,
> Jonathan
> ___
