[ggo-discussion] Re: glGo 1.2 beta
- From: Matthew Rohn <mdrohn@xxxxxxxxxxx>
- To: ggo-discussion@xxxxxxxxxxxxx
- Date: Fri, 11 Mar 2005 18:25:45 -0500
Thanks for the reply, Peter, as usual you're all over the ball ;)
Just a quick thought about the 'load game' bug--perhaps you could put in a
workaround to avoid the bug entirely? Maybe set a flag when all the
necessary resources are loaded for the game board, and check the flag
before loading second or third games.
At 05:36 PM 3/11/2005, you wrote:
> > 1) Launch glGo and click the 'load a game' button
> > 2) Do not load a game from the load SGF file dialog. Keep the dialog open.
> ...snip...
> > 4) The game board doesn't draw. Close the 'load SGF' dialog, and the
> board
> > will draw with limited graphics (b/w, no textures, etc).
>
>Geez... This is nasty. The File-Open dialog is a modal dialog, so it
>will freeze the rest of the application as long it's open. I cannot
>change this as this is the Windows native File-Open dialog.
>When you use the "Load Game" button, the File-Open dialog comes before
>the 3D stuff is initialized. So if you load *another* game, the 3D
>textures wern't loaded yet and you get a half-initialized display.
>Doing above with 2D board crashes glGo.
>Not sure if this is easily fixable. Certainly fixable, but don't know
>how much work that involves. Each 3D and 2D boards use shared resources.
>This causes the mentioned problem when one board didn't init all
>resources, but the second board thinks the resources are available
>because it's the second board - in that case they *usually* are
>available already as the first board loaded them. This might sound
>silly, but saves a lot of memory because you only need to store all the
>textures and images once in RAM and share them among multiple boards. I
>spent quite some efforts to save memory here and I'm not sure if I want
>to sacrifice memory savings for making it more fool-proof.
>So, just don't do it. )
Other related posts:
