Solved

JDK 1.02 - drawImage(x, y, w, h, observer) behaviour

Posted on 1997-10-21
4
204 Views
Last Modified: 2008-03-06
I'm writing a game in Java, for which I create two threads,
one for event and game handling, and one for redrawing and
updating the screen (in the usual way, using an off-screen
GC, etc.). Most of the time I use the drawImage(x, y, obsr)
function for drawing the sprites, because their width and
height is constant. But I wanted to create a dynamic scaling
effect for some of them, so I decided to create a loop where
the width and height (not of the actual image, but that
which I wish to draw on screen) change from 0 to some fixed
numbers and use drawImage(x, y, width, height, obsr) to
draw the scaled image on screen.
The problem is that, while with the 1st drawImage() I get
no flashing and tearing (I already mentioned I'm using an
off-screen GC and a media tracker to eliminate these), with
the scaling version I get significant flashing and tearing
all over the window of the applet and I never get to see the
drawn image!
So, what's going on? Any workarounds?(besides using JDK 1.1)

Thanks in advance
0
Comment
Question by:DGeomel
4 Comments
 
LVL 6

Expert Comment

by:jpk041897
ID: 1229327
Have you looked into double buffering?
0
 
LVL 16

Accepted Solution

by:
imladris earned 100 total points
ID: 1229328
I have found that, contrary to intuition, the image appears to get "reloaded" or rerendered or something internally, if you draw it scaled. This is presumably why MediaTracker provides some scaled variations. Using them cures the problem for me:

      public void adjScale(String f)
      {      int t=pi.getWidth(null);
            width=Util.adjScale(t);
            height=Util.adjScale(pi.getHeight(null));
            scaled=(t!=width);
            if(scaled)
            {      trker.addImage(pi,1,width,height);
                  imgSynch("image "+f+" wouldn't scale");
            }
            return;
      }

      private void imgSynch(String es)
      {      try
            {      trker.waitForID(1);
            } catch(InterruptedException e){};
            if(trker.isErrorID(1))Util.sysError(es,true);
            return;
      }

The adjscale method potentially scales images based on their own size. If it is found that scaling is needed then a scaled variation of MediaTracker.addImage is called and waited on before the image is used.

0
 
LVL 4

Expert Comment

by:russgold
ID: 1229329
You say you are using "an offscreen GC..." - can you explain what you mean?  I generally take "offscreen" to imply a double buffering approach, but GC usually means "garbage collection."

The difference in your approaches is that the scaling takes noticeably more time, so double buffering is essential.
0
 

Author Comment

by:DGeomel
ID: 1229330
To russgold: By "GC" I mean "Graphics Context". I think the term
is not used in Java, but if you've programmed in other platforms
(e.g. Windows) you must've stumbled upon it before.

To jpk: By using an off-screen GC I AM using double-buffering.

To imladris: Thanks, it solved my problem too, but I need some
more clarification:
I want to scale one image for which I use getImage();
If I have to create 10 scaled versions of the same image, I
will call getImage() 10 times with the same filename, and
call the scaled version mediatracker:addImage() for each of them.
But does the file get downloaded 10 times, or only once (and then
processed locally to create the scaled versions)?


0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

By the end of 1980s, object oriented programming using languages like C++, Simula69 and ObjectPascal gained momentum. It looked like programmers finally found the perfect language. C++ successfully combined the object oriented principles of Simula w…
Basic understanding on "OO- Object Orientation" is needed for designing a logical solution to solve a problem. Basic OOAD is a prerequisite for a coder to ensure that they follow the basic design of OO. This would help developers to understand the b…
Viewers will learn about if statements in Java and their use The if statement: The condition required to create an if statement: Variations of if statements: An example using if statements:
Viewers will learn about the regular for loop in Java and how to use it. Definition: Break the for loop down into 3 parts: Syntax when using for loops: Example using a for loop:

758 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now