Indeed, the game scenario you describe is exactly our's :-) I tried  
your b11, it works great!

One more thing if you're digging around in that area would be the  
display resizing primitive (primitiveSetDisplayMode #92). It works  
fine (though I'd prefer the non-stretched variant on my wide-screen,  
but that's nitpicking), except when going out of full-screen mode (or  
quitting Squeak) it should restore the original screen mode, IMHO.  
There is no way I can guess the original setting from inside the image.

- Bert -

Am 23.08.2005 um 02:07 schrieb John M McIntosh:

> MMm, seems we create the window say at 1280x1024, then shift to  
> full screen on the target which is actually 1440x900, then draw,  
> then squeak wakes up anddraws at 1280x1024, then realizes its  
> 1440x900 and draws again. Problem is we've queued up these three  
> draw events and are caching after the first one. The post wait  
> flush then occurs much later...
>
> You get the same behaviour pre 3.8.8bx  it just happens much faster.
> Really the fix should be to build the full screen logic at startup  
> time and report back the correct screen size, versus using the  
> 1280x1024 saved size for the first iteration.
> I suspect there could also be a smalltalk code change for that too.
>
> Also to complicate things we don't actually show the window until  
> the first draw event, so we need to report the saved size I think  
> for the first iteration because the screen
> does not exist quite yet... Mmm lots of complicated things going on  
> for the first screen draw and resize for full screen after image  
> startup. Fixing this issue might take a bit of thought.
> However nice catch I hadn't thought that one would change screen  
> sizes between sessions. Mind you I'll guess that a full screen game  
> would see this quite a bit based on the work station the image is  
> saved on, and the computer you play the game on. .
>
>
> On 22-Aug-05, at 7:28 AM, Bert Freudenberg wrote:
>
>
>
>> When starting up an image saved in different-resolution full- 
>> screen mode (like, running a 1280x1024 image on a 1440x900  
>> screen), a white area to the right is visible for a while. It  
>> seems the VM reports the saved display size to the image rather  
>> than the actual screen size - we center our main UI on the display  
>> screen when starting up, and it appears offset on the 3.8 VM (was  
>> fine in 3.7), like if it was centered in the 1280 screen.
>>
>> - Bert -