Slick Forums

Hello!

When using pedgree from either the jnlp on the main page or the download, it crashes when the colour sliders are moved on the Rendering tab.

The stack trace is:
Mon Apr 06 16:09:07 BST 2009 INFO:Slick Build #244
Mon Apr 06 16:09:07 BST 2009 INFO:LWJGL Version: 2.0b1
Mon Apr 06 16:09:07 BST 2009 INFO:OriginalDisplayMode: 1280 x 1024 x 32 @75Hz
Mon Apr 06 16:09:07 BST 2009 INFO:TargetDisplayMode: 500 x 500 x 0 @0Hz
Mon Apr 06 16:09:08 BST 2009 INFO:Starting display 500x500
Mon Apr 06 16:09:08 BST 2009 INFO:Use Java PNG Loader = true
Mon Apr 06 16:09:08 BST 2009 INFO:Controllers not available
Mon Apr 06 16:09:08 BST 2009 INFO:Starting display 500x600
Mon Apr 06 16:09:16 BST 2009 ERROR:null
java.lang.NullPointerException
at org.newdawn.slick.particles.ConfigurableEmitter.updateParticle(ConfigurableEmitter.java:360)
at org.newdawn.slick.particles.Particle.update(Particle.java:182)
at org.newdawn.slick.particles.ParticleSystem.update(ParticleSystem.java:492)
at org.newdawn.slick.tools.peditor.ParticleGame.update(ParticleGame.java:252)
at org.newdawn.slick.GameContainer.updateAndRender(GameContainer.java:599)
at org.newdawn.slick.AppGameContainer.start(AppGameContainer.java:383)
at org.newdawn.slick.CanvasGameContainer.start(CanvasGameContainer.java:50)
at org.newdawn.slick.tools.peditor.ParticleEditor.<init>(ParticleEditor.java:339)
at org.newdawn.slick.tools.peditor.ParticleEditor.main(ParticleEditor.java:670)
Mon Apr 06 16:09:16 BST 2009 ERROR:Game.update() failure - check the game code.
org.newdawn.slick.SlickException: Game.update() failure - check the game code.
at org.newdawn.slick.GameContainer.updateAndRender(GameContainer.java:605)
at org.newdawn.slick.AppGameContainer.start(AppGameContainer.java:383)
at org.newdawn.slick.CanvasGameContainer.start(CanvasGameContainer.java:50)
at org.newdawn.slick.tools.peditor.ParticleEditor.<init>(ParticleEditor.java:339)
at org.newdawn.slick.tools.peditor.ParticleEditor.main(ParticleEditor.java:670)

I'm using JRE 1.6.0_13 on Vista, with an NVIDIA 8600M GT.

Cheers!

There's a definite issue here to do with AWT EDT thread that used to be the one running the updates - but the Display.setParent() change broke that.

It's a bit of a complicated one. Almost there tho.

Kev

Resolved in SVN.

Kev