Slick Forums

See thread:
http://slick.javaunlimited.net/viewtopic.php?t=1912

_________________
- Gwinnell (irc.freenode.net, irc.chatspike.net)
- Game Jolt Moderator

I'm not sure this is a bug.

As you have discovered, a call to reinit() is probably the way to go since Slick's rendering engine is based more on a retained mode model than an immediate mode model.

Resolution change is a costly operation, so triggering it on the width/height set would create a pretty interesting and unappealing "double operation" side effect since you have to set those parameters in separate properties after the container has been constructed.

Because of this, it's reasonable that you should set your screen sizes and have it perform the resolution change via reinit() once you have all the parameters of your transaction plugged into the game container.

You're not meant to have to call reinit(), thats for an entirely different purporse. However, the ScalabeTest seems to be work still, could you provide a simple test case that shows the issue?

Kev