[Bf-committers] Removing auto registration

[Martin Poirier]

Having panels in the order they are registered is the issue.
We already discussed that last time.

Martin

--- On Sun, 1/16/11, Thomas Dinges <blender at dingto.de> wrote:

> From: Thomas Dinges <blender at dingto.de>
> Subject: Re: [Bf-committers] Removing auto registration
> To: "bf-blender developers" <bf-committers at blender.org>
> Received: Sunday, January 16, 2011, 11:54 AM
> Hi,
> regarding UI Panels, the auto registration caused lots of
> order issues 
> there.  Having panels order in the same way the
> classes are written in 
> the python file is not a good method.
> Therefore +1 for revert.
> 
> Am 16.01.2011 17:51, schrieb Brecht Van Lommel:
> > Hi all,
> >
> > In november there was already a discussion here about
> python class
> > auto registration, but there was no agreement on the
> issue. So I was
> > asked to try to cut the knot here, and I'm proposing
> to revert to
> > manual registration.
> >
> > On first thought, I prefer auto registration, because
> it corresponds
> > to how I envisioned the API working when doing RNA
> design. But I also
> > think the advantages are quite minor, and I agree
> after reading the
> > discussion that on larger projects it can add more
> confusion. Also,
> > there's a number of bugs and issues with it, which
> haven't been
> > resolved and don't seem like they will anytime soon.
> Solving them will
> > also make the API code more complicated.
> >
> > We could discuss the topic further, but it also seems
> that a certain
> > point this is a matter of preference. Campbell can do
> the commit if
> > there's no objection.
> >
> > Thanks
> > Brecht.
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> 
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
>