Hi Goaming,
                  I had tried it and its working. What all u have to do is, u just give the command line parameter like "java PrintCanvas3D file.obj". Here file .obj should be present in ur current directory. Its basically an 3d object file. So after that it will work. If u have any problem after this also then contact me. May be I can help u.
Amit Jindal
-----Original Message-----
From: gaoming fu [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 15, 2001 12:50 AM
To: [EMAIL PROTECTED]
Subject: [JAVA3D] PrintCanvas3D.class does not work

Hi, all:

Did some one try the PrintCanvas3D.class from Java3D API 1.2.1. I tried to print the image using Windows 98 2nd edition and HP LaserJet 2100 Series PCL6-1. I did not get any error message, but it did not print anything for me.

Any ideas?

Gaoming 

>From: Charmaine Lee <[EMAIL PROTECTED]>
>Reply-To: Charmaine Lee <[EMAIL PROTECTED]>
>To: [EMAIL PROTECTED]
>Subject: Re: [JAVA3D] Atomic nature of texture swaps
>Date: Thu, 14 Jun 2001 10:46:00 -0700
>
>David,
>
>Since the texture swap happens within one behavior, the hw texture resources
>will remain untouched, aka, the textures will not be freed and then recreated
>again.
>
>Charmaine Lee
>Java3D Team
>
>
> > Delivered-To: [EMAIL PROTECTED]
> > MIME-Version: 1.0
> > Content-Transfer-Encoding: 7bit
> > X-Priority: 3
> > X-MSMail-Priority: Normal
> > X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
> > Date: Wed, 13 Jun 2001 21:24:25 -0400
> > From: David Yazel <[EMAIL PROTECTED]>
> > Subject: [JAVA3D] Atomic nature of texture swaps
> > To: [EMAIL PROTECTED]
> >
> > Question for the Sun Engineers :)
> >
> > If I have two shapes, one with texture A and one with texture B and within
> > one behavior I swap their textures like this:
> >
> > Texture a = shapeA.getAppearance().getTexture();
> > shapeA.getAppearance().setTexture(shapeB.getAppearance().getTexture());
> > shapeB.getAppearance().setTexture(a);
> >
> > Can I be safe in assuming that this will not result in texture "a" from
> > being unbound from the card and then sent back over? In other words if you
> > ignore the texture binds until you have to send the data to the next frame,
> > and at that point compare what you know is cached there with the needs of
> > the objects are... then we are safe. But alternatively if you handle a
> > Appearance->texture reference count and flag the texture for removal as soon
> > as the reference count reaches zero, then the texture could be dropped even
> > though it is going to be referenced by another shape.
> >
> > Dave Yazel
> >
> > ===========================================================================
> > 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".
>
>===========================================================================
>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".


Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.

=========================================================================== 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".

Reply via email to