[Bf-taskforce25] Moving RNA Struct inheritance to iteration time

[Brecht Van Lommel]

Hi,

Thanks for the patch! Will review and commit.

Regarding what was discussed in the meeting, will repeat here in short 
what was the conclusion for completeness. Splitting the storage for 
inheritance is fine, I also need it myself for the C api.

Groups are useful for organizing the RNA outliner better. It's not 
clear yet however how this works with the nested structs (those get 
rid of ray_mirror_ prefixes in python code, which does not seem a good 
idea for groups to do as well). How groups would affect automated UI 
generating is also not clear yet, if it is sufficient information, or 
if we should not try to solve such things at the RNA level. I need to 
think about this a bit more..

Thanks,
Brecht.

vekoon wrote:
> Hi brecht,
> as you agreed on channel about moving struct inheritance for properties 
> to iteration time and because I had some time tonight I implemented it 
> as to avoid you some work (well not much, depends especially on how many 
> mistakes I made). Hope you don't mind. Here's the patch: 
> http://vekoon.googlecode.com/files/rna_struct_inheritance_1.0.patch
> Oh by the way, I grepped through the code in search for 
> RNA_struct_defined_properties and noticed that no code uses it, which is 
> good because now it returns only the properties that strictly belong to 
> that struct.
> 
> Also the patch is for others to try out if you have time. Although I 
> tested it a bit, more testing is always better.
> As a side note, now properties show up in the outliner ordered by struct 
> inheritance so you'll always see (for instance) name and modifier 
> settings before the properties specific for the actual modifier type 
> which to me looks nicer than it was before.
> _______________________________________________
> Bf-taskforce25 mailing list
> Bf-taskforce25 at blender.org
> http://lists.blender.org/mailman/listinfo/bf-taskforce25
> 
>