From: Fred Dech (fred@cerulean.bvis.uic.edu)
Date: 05/12/2000 07:07:28
hi again.
you guys are probably at a conference, or something. because my question
wasn't trivial. if i re-code with the new Performer node, i *really need
to know* that it's worth my time. because it will require quite a few
hours/days of work to recode and then modify the new node so that it can
do what is needed. then there's the debugging...
thanks.
--fred
Forwarded message:
>
> hi.
>
> i'm finally at the point of upgrading Volumizer/Performer applications to
> use the most current Volumizer release.
>
> there's not much documentation with the newest Performer node example.
> i can tell that it takes a radically different approach than the
> earlier Volumizer/Performer node.
>
> why is it better? it's also not at all clear to me that there's an avenue
> in the new node for creating an interface for passing data, etc., from the
> computational process to the graphics process (and vise-versa) after volume
> initialization. the earlier Performer node, while cumbersome and not 100%
> reliable, has such an interface.
>
> thanks.
>
> --fred
> --
> Fred Dech fdech@uic.edu
> VRMedLab
> (312) 413-3092: fax (312) 996-8342
> "We'll burn that bridge when we come to it." JL
This archive was generated by hypermail 2b29 : Fri May 12 2000 - 08:06:47 PDT