your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Answered by Madhurima , an ibibo Master, at 11:58 AM on August 27, 2008

well, you load an image (using java.awt.Toolkit.getImage), the function
returns immediately, and the image is loaded asynchronously. This means
that sometimes an image isn't ready to be drawn, because it hasn't yet
loaded. Depending on when the image is loaded, and when it is drawn, the
problem can be intermittent and hard to track down.

If your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Once you start the wait, your application will block until the image has
loaded. Then, you can call java.awt.Graphics.drawImage to display the
image to your applet or application.


For more details , Please visit the source site :

http://www.javacoffeebrea k.com /newsletter/1999/jcbissuevolum e2iss ue3.txt

Answered by Nidhi Singh , an ibibo Master, at 11:48 AM on August 25, 2008

you load an image (using java.awt.Toolkit.getImage), the function
returns immediately, and the image is loaded asynchronously. This means
that sometimes an image isn't ready to be drawn, because it hasn't yet
loaded. Depending on when the image is loaded, and when it is drawn, the
problem can be intermittent and hard to track down.

If your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Once you start the wait, your application will block until the image has
loaded. Then, you can call java.awt.Graphics.drawImage to display the
image to your applet or application.


For more details , Please visit the source site :

http://www.javacoffeebrea k.com /newsletter/1999/jcbissuevolum e2iss ue3.txt

Answered by Ashish Yadav , an ibibo Wizard, at 1:07 PM on August 20, 2008

you load an image (using java.awt.Toolkit.getImage), the function
returns immediately, and the image is loaded asynchronously. This means
that sometimes an image isn't ready to be drawn, because it hasn't yet
loaded. Depending on when the image is loaded, and when it is drawn, the
problem can be intermittent and hard to track down.

If your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Once you start the wait, your application will block until the image has
loaded. Then, you can call java.awt.Graphics.drawImage to display the
image to your applet or application.


For more details , Please visit the source site :

http://www.javacoffeebrea k.com /newsletter/1999/jcbissuevolum e2iss ue3.txt

Answered by Shobhit , an ibibo Master, at 1:07 PM on August 18, 2008

I am agree with alok answer give a look at his answer........

Answered by shaista , an ibibo Master, at 10:11 AM on August 01, 2008

hello friend
you load an image (using java.awt.Toolkit.getImage), the function
returns immediately, and the image is loaded asynchronously. This means
that sometimes an image isn't ready to be drawn, because it hasn't yet
loaded. Depending on when the image is loaded, and when it is drawn, the
problem can be intermittent and hard to track down.

If your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Once you start the wait, your application will block until the image has
loaded. Then, you can call java.awt.Graphics.drawImage to display the
image to your applet or application.


For more details , Please visit the source site :

http://www.javacoffeebrea k.com /newsletter/1999/jcbissuevolum e2iss ue3.txt

Answered by Rupesh , an ibibo Citizen, at 9:14 PM on July 31, 2008

Well Swati , When
you load an image (using java.awt.Toolkit.getImage), the function
returns immediately, and the image is loaded asynchronously. This means
that sometimes an image isn't ready to be drawn, because it hasn't yet
loaded. Depending on when the image is loaded, and when it is drawn, the
problem can be intermittent and hard to track down.

If your application or applet MUST display the image before doing
anything else, you can have it wait until the image is fully loaded. An
animation applet, for example, may not have any useful work to do until
the image(s) are loaded. To wait for images, you need to use the
java.awt.MediaTracker class.

MediaTracker allows you to register an image with the tracker, and have
your application or applet wait until the image is ready. Note that this
isn't limited just to applets loading images over a network - from my
own experience an application it can happen loading a small
(<100 bytes) image from a local filesystem.

To register an image, you assign it an image number, and call the addImage
method. Then you can call the waitFor(int) or waitForAll() methods.

// Pass media tracker any component (such as a canvas or an applet)
MediaTracker tracker = new MediaTracker( this );

// Add images
tracker.addImage ( myImage1, 0);
tracker.addImage ( myImage1, 1);

// Wait for images
try {
tracker.waitForAll();
} catch (InterruptedException ie) {}

Once you start the wait, your application will block until the image has
loaded. Then, you can call java.awt.Graphics.drawImage to display the
image to your applet or application.


For more details , Please visit the source site :

http://www.javacoffeebreak.com /newsletter/1999/jcbissuevolume2iss ue3.txt

Answered by Alok Gupta , an ibibo Guru, at 5:38 PM on July 31, 2008

may be some saving options is disturb do configuration as default all setting preset all tools. and try again.

Answered by Atul , an ibibo Specialist, at 1:09 AM on July 31, 2008