The Puzzle Page

Raab, Andreas Andreas.Raab at disney.com
Fri Dec 15 07:42:18 UTC 2000


Dan,

A couple more notes:

> 1.  Open, eg, a browser (with pop-out scrollbars).  Move your 
> cursor in and out of a list pane, and notice that the 
> contents do not get rewritten (no damage flash).  Now move 
> your cursor in and out of a text pane.  Notice that the 
> entire text contents gets rewritten.  Although the region of 
> the selection does get redisplayed, it should not bve 
> necessary to repaint the entire text area.  Fix this.

See TextMorph>>fit last line where it says:

	self changed. "Too conservative: only paragraph composition
				should cause invalidation."

remove this line and you don't get these flashes anymore. Except that typing
doesn't work correctly (I don't know where to get the right invalidation
regions here).

> 2.  Open any two browsers.  Click first in one, then the 
> other.  Note that the entire window gets repainted not once 
> but twice.  Fix this.

Bob's observation seems to be the key. Remove those "self changed" from
#stopSteppingSelector: and #stopStepping and it goes away.

> 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.

  - Andreas





More information about the Squeak-dev mailing list