Hello Bill,
thanks for your answers.
At the moment we are "fighting" on another front of the project. So, if we get
back to the VisAd part, I will post further details here.
One short note to the cursor string issue: All lines of the string were drawn
in the "first line" one above the other.
This hole topic turnes more and more into a Java3D problem than a VisAD one. We
still get trouble with this second view and its transformation. Before we
haven't find a proper way to do this with a simple "helloworld" application
it's senseless go on with the VisAD part. So, don't worry about the cursor
string. I'am pretty sure the artefact was created by our wrong method to add
this second view/-transformation.
As I said, I will update you concerning this multi-view topic as soon as it
becomes a VisAD issue again.
Regards,
Finn
----- Original Message -----
From: "Bill Hibbard" <billh@xxxxxxxxxxxxx>
To: "Finn Klug" <finn.klug@xxxxxxxxx>
Sent: Tuesday, May 06, 2003 12:38 AM
Subject: Re: Adding 2nd view for holoscreen floor projection
> I said:
>
> > You can correct the incorrect cursor string by over-riding the
> > drawCursorStringVector(VisADCanvasJ3D) method in DisplayRendererJ3D.
> > You can pass your other VisADCanvasJ3Ds to your extension of
> > DisplayRendererJ3D by another method. With a little luck you can
> > just put the existing drawCursorStringVector() code inside a loop
> > over your VisADCanvasJ3Ds (might be a bit more complex than that).
>
> Oops. drawCursorStringVector(VisADCanvasJ3D) is invoked from
> VisADCanvasJ3D.renderField() as drawCursorStringVector(this),
> so no need to pass a list of your VisADCanvasJ3Ds to your
> extension of DisplayRendererJ3D by another method. Since the
> drawing in drawCursorStringVector() is al immediate mode,
> it hopefully should only apply to the invoking VisADCanvasJ3D.
> If this doesn't work, let me know in more detail how the
> cursor string is incorrectly drawn.
>
> Good luck,
> Bill
>
>
