Re: Why does DEF do instancing?

nelson18@llnl.gov
Sun, 15 Oct 1995 14:55:42 -0700


>
>DEF blah blah {
>}
>
>DEF bleh bleh {
>}
>
>Separator {
> USE blah {}
> USE bleh {}
>}
>

It's always bothered me that DEF both defines and uses the object
and makes it hard to utilize libraries of objects. What are the
objections to just having DEF define an object? Thus, to see
it, you must USE it. This way, you could esad in a library of
pre-defined objects and only actually use the ones that you
wanted in a scene (I know this is wasteful).

I ran into this issue when creating some objects that I wanted
to define in a generic sense and not have to worry about placing
until later when I had more info.

This scheme also avoids the "register the `last'" issues reguarding
"what is `last'?"

Scott Nelson

-- 

+----------------------------------------------------+ |Scott D. Nelson B131 Rm2074 3-1250 | |Lawrence Livermore National Laboratory | |7000 East Ave., L-153 Livermore CA 94550 | |email: nelson18@llnl.gov http://www-dsed.llnl.gov/ | +----------------------------------------------------+


  • Next message: Mike Heck: "Re: TGS Webspace"
  • Previous message: Mike McCue : "Re: ADMIN: VRML + JAVA - A Wedding"