As documented in the release changelog here:http://lwjgl.org/changelog.phpKeyboard.enableBuffer() was removed from the public API.Questions:Why was it removed? Will it resurface elsewhere or is gone for good?Is there a replacement in 0.95? It's incredibly handy.Regards,Owen Butler
I have the same problem numberR mentioned above. I can get the failed dependecy to go away, but when I try to use javax.imageio.ImageIO.read() to read in PNG files. It blows up with a newer depenedency failure for the same libmawt.so? anyone got any ideas?I am running FC3 on AthlonXP with jdk1.5.0_01[edit] I finally got it to work by copying the so's into /opt/jdk1.5.0_01/jre/lib/i385 and taking out the -Djava.libra.... stuff. perhaps the jre doesn't know which libmawt to use after some new change to lwjgl? (motif, headless and xawt exist)
Quote from: "Zero"I have the same problem numberR mentioned above. I can get the failed dependecy to go away, but when I try to use javax.imageio.ImageIO.read() to read in PNG files. It blows up with a newer depenedency failure for the same libmawt.so? anyone got any ideas?I am running FC3 on AthlonXP with jdk1.5.0_01[edit] I finally got it to work by copying the so's into /opt/jdk1.5.0_01/jre/lib/i385 and taking out the -Djava.libra.... stuff. perhaps the jre doesn't know which libmawt to use after some new change to lwjgl? (motif, headless and xawt exist)I think I found a fix to the problem. Calling Toolkit.getDefaultToolkit() before loading the lwjgl native lib seems to work. The fix is added to CVS, but you can easily add the line to your applications in the meantime. - elias
it worked for me as well by calling Toolkit.getDefaultToolkit() before loading the lwjgl native lib. is Toolkit.getDefaultToolkit() necessary for all AWT application?