LWJGL 0.95 Released

[baegsi]

Thanks, that's great. No need to rush though, I can still use .94 until then or do what you suggested. It's just good to know that the error is not on my side

[CaptainJester]

I have all devil related dlls in my path: DevIL.dll, ILU.dll and ILUT.dll, they are all located in one folder that I reference via -Djava.library,path...

Sorry.  DevIL doesn't check the java.library.path yet.  I will fix that tonight, but for now you have to put the dlls in your path or in the same spot you are executing from.

I think I am wrong.  I think it is supposed to automatically check the java.library.path if it exists.  Can someone confirm this?

Thanks.

[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)

[elias]

The bug is described here:

http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4976297

What is puzzling is that it is marked as "fixed" in beta 2, but the problem is obvious still there.

- elias

[elias]

I have now re-posted the bug. We'll see what happens then.

- elias

[ap_kelly]

I noticed that this isn't a simple drag-and-drop replacement for v0.9.4. The method Keyboard.enableBuffer() seems to have been removed.

Caused by: java.lang.NoSuchMethodError: org.lwjgl.input.Keyboard.enableBuffer()V

Was this mentioned in the changelog or release notes?

Cheers,

Andy.

[Matzon]

it's all in the changelog - however, not in the relase notes

[ap_kelly]

Would it be possible in future to mark these methods as deprecated, and only remove them in v1.0 that way I don't have to go through my entire code suit with each release of LWJGL and make changes. This would allow me to choose when to remove the redundant code and if the Javadoc said it wouldn't be present at v1.0 I'd have an indication of when I had to remove it by.

Just ripping code out of the public API is very annoying to the developers, especially since the enableBuffering() method is likely to have been used by everyone!

Thanks,

Andy.

[blue_tomato]

Great work!

Just out of curiosity, how can my program read the current version number of lwjgl it is running?

[theBohemian]

This libmawt problem looks familiar. It showed up first in one of the early betas (beta1?) of JDK1.5.

The funny thing is, that is really fixed in beta2 and 1.5.0. At least I have not the problem some people are describing with the *first* release of JDK1.5.0

[Matzon]

Just out of curiosity, how can my program read the current version number of lwjgl it is running?

It can't. Unless you uses Introspection and grab the

private final static SysImplementation implementation;

and call getNativeLibraryVersion on it. However you're on your own when you do that kind of stuff - and it will probably break.

Do we need a public method for getting the version ?

[numberR]

The funny thing is, that is really fixed in beta2 and 1.5.0. At least I have not the problem some people are describing with the *first* release of JDK1.5.0

i just downloaded the latest version of JDK 1.5.0, but no luck. maybe linux distribution dependent issue because i also use Fedora Core 3 as well as Zero. What do you use, theBohemian?

[nea]

Wrong date!

LWJGL 0.95 released! Tuesday, January 25th, 2004 <------
0.95 released. Lots of fixes. Thanks everybody. Please check this thread for more info regarding the release

[Matzon]

meh, copy paste bug, will fix tonight

[OwenButler]

As documented in the release changelog here:

http://lwjgl.org/changelog.php

Keyboard.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