On Tue, Nov 2, 2010 at 2:44 AM, Martin Poirier the...@yahoo.com wrote:
Hi,
--- On Mon, 11/1/10, Campbell Barton ideasma...@gmail.com wrote:
But now its become a problem that we have more complicated
situations
which I dont think can be handled well automatically...
1) registering classes
--- On Mon, 11/1/10, Matt Ebb m...@mke3.net wrote:
On Tue, Nov 2, 2010 at 2:31 PM,
Martin Poirier the...@yahoo.com
wrote:
def fun():
class NewPropertyGroup(bpy.types.IDPropertyGroup):
pass
bpy.types.Scene.new_property =
PointerProperty(type=NewPropertyGroup, name=Stuff,
On Fri, Oct 29, 2010 at 10:06 PM, Nathan Vegdahl ces...@cessen.com wrote:
On the contrary. Having half-defined subclasses of RNATypes breaks
the Liskov substitution principle.
How? The RNATypes themselves are not fully defined (e.g. you can't
use bpy.types.Panel directly). Making a derived
Hi,
--- On Mon, 11/1/10, Campbell Barton ideasma...@gmail.com wrote:
But now its become a problem that we have more complicated
situations
which I dont think can be handled well automatically...
1) registering classes which have properties which are
themselves are
rna classes... and so
On Tue, Nov 2, 2010 at 1:44 PM, Martin Poirier the...@yahoo.com wrote:
4) dynamically defined classes/operators are also a case
where auto-registration becomes more tricky then its worth.
If you're talking about the cases where people were using type() to
initialize a class, that's very
On the contrary. Having half-defined subclasses of RNATypes breaks
the Liskov substitution principle.
How? The RNATypes themselves are not fully defined (e.g. you can't
use bpy.types.Panel directly). Making a derived class of
bpy.types.Panel that also can't be directly used hardly violates
Hi Nathan,
--- On Thu, 10/28/10, Nathan Vegdahl ces...@cessen.com wrote:
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.
From my personal experience I did not had any problem when we changed
for autoregistration of panels, but I have issue when desabling and
reenabling the addon due to custom properties. This is not related to
autoregitration as it this happaned even before this change.
Xavier
2010/10/28 Martin
...or even have a register() method in classes that overrides the default
automagic-registering and perhaps a call to super().register() if you need
the default behavior after the class-specific stuff?
Or not, just throwing stuff out there.
Dan
___
