Timothy M. Shead wrote:
> Bart Janssens wrote:
>> On 5/4/08, Joaquín Duo <
hoakoduo@...> wrote:
>>
>>> Anyway, I think the idea of adding a layer int32_t property for the
>>> Meshinstances (and some other nodes, like cameras, grids, ligths) could be
>>> used
>>> in future C++ implementations. Also this way an object could be part of
>>> several
>>> layer having multiple properties.
>>>
>> It's a good idea, but I think it should be formalized in an interface
>> that provides access to the collection of layer properties. That way,
>> it's easy to query if
>> - an object supports layers
>> - what its layer properties are
>>
> Layers are really just one type of grouping mechanism, one that happens
> to have some related semantics drawn from 2D drafting. Adding
> group-related data to nodes won't scale for the same reason visibility
> flags don't scale. Suggest you take a look at
>
>
http://www.k-3d.org/wiki/Node_Grouping_DesignGood point. Thanks for the tip!
I guess visibility groups, groups and collections could all be merged together,
isn't it?
Also this may help on the problem hiding materials objects, or you prefer
another mechanism?
Cheers!
Joaquín
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone_______________________________________________
K3d-development mailing list
K3d-development@...
https://lists.sourceforge.net/lists/listinfo/k3d-development