On Saturday 02 August 2003 02:59 pm, Derek Brans wrote:
> I'm getting a debugger popping-up intermittently while just moving
> through the browser.  Has anyone seen this?

> MouseOverHandler>>noticeMouseOver:event:
>   leftMorphs:  nil
...
> MouseOverHandler>>processMouseOver:

Well, it's clear that something ate leftMorphs. Considering that in a 
stock image those are the only two methods writing into that instance 
variable, you've got a problem.

It would be interesting to trace how that occurred. Perhaps if 
ActiveEvent == lastMouseEvent and there were no events in 
processEvents, this would happen. But it looks like you'd have to 
call the processMouseOver: twice to get this to happen.

You could change noticeMouseOver:event:  to this:

noticeMouseOver: aMorph event: anEvent
	"Remember that the mouse is currently over some morph"
	(leftMorphs notNil and: [ leftMorphs includes: aMorph]) 
		ifTrue:[leftMorphs remove: aMorph]
		ifFalse:[enteredMorphs nextPut: aMorph].
	overMorphs nextPut: aMorph.

-- 
Ned Konz
http://bike-nomad.com
GPG key ID: BEEA7EFE