Justin Couch wrote:
>...
> However, you
> may have the severly limiting factor that a single appearance
generally
> means a single colour for every single object (you need a separate
> appearance for each texture you want to use or different Material
> config).
>...
Yes, what I really would like is for multiple Appearances to reference a
single PolygonAttributes and TextureAttributes, so that I can have
individually change the mode with one method call on the Attributes
object. I can experiment to see whether this will work for
PolygonAttributes. Unfortunately, for textures, the enable flag is part
of the Texture object. It seems like it should be in TextureAttributes
or even in PolygonAttributes, not in Texture.
>...
> The problem is, does the parent Appearance class get copied like the
> Transform3D does, or does it get referenced. Let's look at the set
> method doc:
>...
I did mention this general problem to the Java3D team at the recent
SIGGRAPH BOF session for Java3D, and I requested they specifically state
in the Javadocs whether the arguments to a method were being referenced
or copied. They said that there were some general rules that were
followed, mostly, so knowing those would help out in most situations.
They also said they'd see about making it more clear in the Javadocs.
So perhaps things will improve.
--
Ellery Chan <[EMAIL PROTECTED]>
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA3D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
