Skip to main content

Gui generator re-generate my maze if I change the current window dimensions(Java)



Given the following code :







class Game() {





private Shell shell;



public Game(Display display,int level)

{







shell.addPaintListener(new ExmaplePaintListener());



shell.setText("Basic shapes");

shell.setSize(900,900);

shell.setLocation(45, 45);

shell.open();



while (!shell.isDisposed()) {

if (!display.readAndDispatch()) {

display.sleep();

}

}

}

}







The listener :







private class ExmaplePaintListener implements PaintListener {



public void paintControl(PaintEvent e) {







drawMaze(e);

placeTreasuresInMaze2(e);

e.gc.dispose();







}

}







and the method that draw the maze







private void drawMaze(PaintEvent e) {



// this method creates a new maze and draw it using GUI Java



}







My problem is that after the window of the maze is created , if I use the mouse to change the dimensions of the window , then the method drawMaze creates a new maze in the current window . This is obviously a bug , so where is my mistake ? maybe something with the Constructor of the Game class ?





Regards Ron


Comments

  1. In general, the paint event happen after resize events. So if you resize using either the mouse or even programmatically, then the drawMaze() function will be called. I think you should not create the maze in drawMaze(), or at least make a lazy initialization. That's because a maze will be created each time the window is painted, which occurs every time you resize the window, you move the window, you hide some part of the window, you change focus, etc... That's a lot of mazes :D.

    EDIT:
    The paint event suggest you that the display has changed, and that the change is likely to affect the portion of the screen you are painting on. So few things:


    During a paint event you want to do only one thing: painting. So don't call garbage collection. In general calling the Gc is not a good idea, and moreover in a Listener it will just crush the performance.
    The event will not change the state of your Maze. So you should represent your maze using a state. One part is fixed, like the walls, the other side is variable, like the agent position inside the maze. Each time you modify the state, you ask a repaint.
    If you skip a paint event, the screen will be blank.


    For example if your maze is too big to fit on the screen, you use the paint event to paint only one part, etc..

    ReplyDelete

Post a Comment

Popular posts from this blog

[韓日関係] 首相含む大幅な内閣改造の可能性…早ければ来月10日ごろ=韓国

div not scrolling properly with slimScroll plugin

I am using the slimScroll plugin for jQuery by Piotr Rochala Which is a great plugin for nice scrollbars on most browsers but I am stuck because I am using it for a chat box and whenever the user appends new text to the boxit does scroll using the .scrollTop() method however the plugin's scrollbar doesnt scroll with it and when the user wants to look though the chat history it will start scrolling from near the top. I have made a quick demo of my situation http://jsfiddle.net/DY9CT/2/ Does anyone know how to solve this problem?

Why does this javascript based printing cause Safari to refresh the page?

The page I am working on has a javascript function executed to print parts of the page. For some reason, printing in Safari, causes the window to somehow update. I say somehow, because it does not really refresh as in reload the page, but rather it starts the "rendering" of the page from start, i.e. scroll to top, flash animations start from 0, and so forth. The effect is reproduced by this fiddle: http://jsfiddle.net/fYmnB/ Clicking the print button and finishing or cancelling a print in Safari causes the screen to "go white" for a sec, which in my real website manifests itself as something "like" a reload. While running print button with, let's say, Firefox, just opens and closes the print dialogue without affecting the fiddle page in any way. Is there something with my way of calling the browsers print method that causes this, or how can it be explained - and preferably, avoided? P.S.: On my real site the same occurs with Chrome. In the ex