Jim Graham wrote:
I'm still somewhat puzzled, though. If by hiding a component tree
you mean, for example, moving another window in front,
or icon-izing, then we do this all the time,
and have *never* seen any problems. Not once in
almost 5 years (!) of doing this stuff. I realize
Hello all,
I should have probably mentioned I am just using awt, no swing so the
paintImmediately() is not an option. I don't want to deal with the
1.2.2 pugin-in security issues that go with swing.
Direct calls to update don't seem to work either. Once again, if I
include a main() in my applet
: [JAVA2D] Help! Paint STILL not updating (thread issues)
Hello all,
I should have probably mentioned I am just using awt, no swing so the
paintImmediately() is not an option. I don't want to deal with the
1.2.2 pugin-in security issues that go with swing.
Direct calls to update don't seem to work
I am trying to display video from a file.
My code is structured like...
while (true) {
getHeader()
doLotsOfMath();
frameNumber++;
update(getGraphics());
}
What have you done to deal with either of these two issues:
- throttling your updates
- making sure you
Hi Bill,
Why should you write
g = getGraphics()
each time you want to update it?
It's the most foolproof way.
Why shouldn't you fix g at some early point in the component's
life?
You can, but there are a number of circumstances in which a Graphics
can become invalid and then you are
();
Toolkit.getDefaultToolkit().sync();
Hope this helps
mick :)
You wrote:
From: Abel Rauch [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Date: Thu, 30 Mar 2000 11:47:58 PST
Subject: Re: [JAVA2D] Help! Paint STILL not updating (thread issues)
I am trying to display video from a file.
My code is structured
Jim Graham wrote:
How slow? Which version of which VM? getGraphics performance continues
to be an area that we are working on. If you are fixing your max frame
rate at 30 or so frames per second, is it slow enough to affect that?
Even on some of our worst performing implementations
Undetermined origin c/o LISTSERV administrator wrote:
Abel,
Don't think this'll fix your problem, but my understanding of AWT is that you should
be calling the repaint() method, not the update() method.
By calling update I think you are doing your repaint in the current thread, whereas
if
Don't think this'll fix your problem, but my understanding of AWT is that
you should be calling the repaint() method, not the update() method.
This is definately the recommended course of action and the safest bet
generally. Be careful not to make assumptions about when your update
method
