Re: a tight game loop in Swing
Knute Johnson wrote:
Lew wrote:
John B. Matthews wrote:
This reminds of an example adduced by Knute Johnson:
<https://groups.google.com/d/msg/comp.lang.java.gui/aBy_DZFvg2M/-T9aWOwBM-QJ>
Ten points for using the word "adduced".
There are some EDT violations in the cited code's 'main()' routine.
Here's the updated code with that fixed.
import java.awt.*;
import java.awt.event.*;
import java.awt.geom.*;
import java.awt.image.*;
import java.lang.reflect.*;
import javax.swing.*;
public class test3 extends JPanel implements Runnable {
volatile BufferedImage bi;
volatile long then;
I am curious what motivated the choice of 'volatile'.
In my own case I will sometimes speculatively use 'volatile' to mark fields
not essential to state despite that the class does not implement
'Serializable'. While this violates the rigid rule prohibiting superfluity, I
aver that the marker aids reasoning about the state in such cases.
This doesn't seem to be that.
--
Lew
Honi soit qui mal y pense.
http://upload.wikimedia.org/wikipedia/commons/c/cf/Friz.jpg