The Coffee Quest 3 Problem page 4

First attempt at fixing

With the potential culprit in hand, the problem now became the task of verifying that I had indeed found the problem and finding a way of fixing the problem. Verifying the problem could be done by use of the console. By including a line of code that prints the time when the grabbing begins, and a line that prints out the time when the grabbing ends, you will have the information needed to verify the problem. Now, if the reason for the problem was due to the fact that the image wasn't preloaded, then preloading the image should solve the problem. So in addition to adding the print statements, I also preloaded the images. After all, if you look at the following code, it is an easy thing to do.

MediaTracker tracker = new MediaTracker(a);
iTextures = a.getImage(a.getDocumentBase(), cfg.getStringProperty(TILESET, "tiles.gif"));
tracker.addImage(iTextures, 1);
try
{
- tracker.waitForAll();
}
catch (Exception e)
{
- System.err.println("Problem loading textures");
}

Now, hopefully the problem has been solved, but I have some debug code in the program just in case it isn't. So rebuild the jar file and post it on my site. Open the games page, and the problem persists.

Am I sure that I am looking at the right problem? Well, we did add those two lines of code. A quick look at the java console will tell me if I am looking in the right direction. The result, indeed the grabbing is occurring during the long delay! But why is pixel grabber reloading the image every time? Pixel Grabber is probably requesting that the image producer send it a fresh image. The image producer, unfortunately, is taking this request to the extreme by reloading the image from the web site.

Coffee Quest 3 Problem page 4 of 5