next »

[Marvin Fröhlich]

If you exited your game by calling System.exit( 0 ), please don't do this anymore. It doesn't clear the screen and doesn't destroy the Display context correctly. Do it like this:

Code:

public class MyGame extends RenderLoop
{
    public void onKeyReleased(int key)
    {
        switch (key)
        {
            case KeyCode.VK_ESCAPE:
                this.end();
                break;
        }
    }
   
    public MyGame()
    {
        super( 128L );
       
        ...
       
        this.setStopOperation( StopOperation.DESTROY_AND_EXIT );
       
        this.begin();
    }
}

You may override the exit() and/or destroyAndExit() method(s) of the RenderLoop class to change/extend the exit behavior.

Marvin

[hawkwind]

Nice...on the subject of clear screens.  Is there any way to wipe the initial window prior to the display of it.  I find in my game the last rendered view is displayed the next time the game starts.  Or will the above handle this??

[Marvin Fröhlich]

Nice...on the subject of clear screens.  Is there any way to wipe the initial window prior to the display of it.  I find in my game the last rendered view is displayed the next time the game starts.  Or will the above handle this??

Exactly. The above should do the trick .

Marvin

['n ddrylliog]

Shouldn't it be the default ?

[Marvin Fröhlich]

Shouldn't it be the default ?

Would be cool. But it would change the behaviour on existing games. So, no

['n ddrylliog]

Shouldn't it be the default ?

Would be cool. But it would change the behaviour on existing games. So, no

Come on, it doesn't change lots of things ? But I guess you're right. So no.

[starscream]

i can not agree:
you do not have reached the 1.0-status - so you do not have a stable api!
change what ever you want and do it to have a clean, simple and stable one!
also the deprecated methods should be removed!
as long as it you document the changes their sould not be any problems that could not be solved.

if you ever release the 1.0 you can not change the api, but for now: use the force, luke

[Marvin Fröhlich]

i can not agree:
you do not have reached the 1.0-status - so you do not have a stable api!
change what ever you want and do it to have a clean, simple and stable one!
also the deprecated methods should be removed!
as long as it you document the changes their sould not be any problems that could not be solved.

I agree partly. I will change the default of this thing. But we will remove the deprecated methods immediately prior to 1.0 release. No it is much easier for the users to see, that there's something deprecated and can start porting their code when they are ready for it. But I guess it is annoying, if one has to port each day.

And we can still change the API after 1.0 release. But then it has to be done in a higher minor version 1.(x+1).y

if you ever release the 1.0 you can not change the api, but for now: use the force, luke

Ah, a brother . But I prefer the dark side .

Marvin

[Marvin Fröhlich]

Now the default StopOperation is DESTROY_AND_EXIT. Please be aware of it.

Marvin