Karl,

I did notice and it's already fixed (though not yet in the public update
stream). The thing is that the balloon morph should force a layout
computation before it goes onscreen. But thanks for pointing this out!

  - Andreas

> -----Original Message-----
> From: Karl Ramberg [mailto:karl.ramberg at chello.se]
> Sent: Friday, December 15, 2000 3:20 PM
> To: squeak at cs.uiuc.edu
> Cc: recipient list not shown
> Subject: Re: The Puzzle Page
> 
> 
> 
> 
> Bob Arning wrote:
> > 
> > On Thu, 14 Dec 2000 23:42:18 -0800 "Raab, Andreas" 
> <Andreas.Raab at disney.com> wrote:
> > >> 4.  Open one morphic project within another.  Enter the sub
> > >> project.  Then return to the previous project.  Notice that
> > >> on each transition the project entry code painstakingly
> > >> paints the entire screen for the new project, and then
> > >> repaints it once the project is entered.
> > >
> > >I was unable to reproduce this. I found that only flap 
> tabs and the top
> > >window are redrawn when the project transition is 
> completed and that seems
> > >okay to me. You might have been spoiled by using global 
> flaps - since these
> > >get added by a project transition chances are that the 
> regions get merged
> > >(this may happen in response to the activation of the new 
> top window which
> > >will invalidate a possibly large portion of the display) 
> which may then look
> > >like a full screen redraw.
> > 
> > Another possible candidate for excessive drawing is
> > 
> > SketchMorph(Morph)>>invalidRect:from:
> > SketchMorph(Morph)>>invalidRect:
> > SketchMorph(Morph)>>changed
> 
> 
> I don't know if I just missed this in your reports but
> when a ballonhelp ballon pops up it flashes a great deal of 
> the screen.
> Like for the little menu in systemwindows that are allways enabled 
> for ballon help.
> Karl
>