Thanks. I think that for the MouseOverHandler it would be good to know if this is related to Sensor changes. Mike what you think? Stef On Jun 4, 2009, at 1:53 AM, Gary Chambers wrote:
That's an old one... a bit late here so look it up on Mantis. ANYTHING that manipulates morphs etc. in a process other than the UI process is liable to break in one way or another.
The mouse over handler is just one of the most frequent (most events)...
The workaround we have is to do the nil check. A Workaround though...
Regards, Gary ----- Original Message ----- From: Hernan Wilkinson To: Pharo-project@lists.gforge.inria.fr Sent: Wednesday, June 03, 2009 8:59 PM Subject: Re: [Pharo-project] an odd bug
I think I founded the problem... I don't know what makes it happen or how to solve it yet :-) But the problem is a raise condition. In method MouseOverHandler>>processMouseOver: anEvent the instance variable leftMorphs is set to nil, but when accessing that variable there is no check for nil. So, if processMouseOver: anEvent is running in two different processes, in one leftMorphs could set to nil while in the other process is still been used...
Is it possible for processMouseOver: anEvent to be evaluated in more than one process? If that is true, so that is the problem... if not, nothing makes sense...
2009/6/3 Mariano Martinez Peck <marianopeck@gmail.com> I didn't know that. logDebuggerStackToFile is the option?
It's strange because this is enable by default and I don't think Sean change it.
On Wed, Jun 3, 2009 at 5:39 PM, Nicolas Cellier <nicolas.cellier.aka.nice@gmail.com
wrote: This is controlled by a Preference setting...
Nicolas
2009/6/3 Sean Allen <sean@monkeysnatchbanana.com>:
dont have one. there isnt any debug.log in the directory with the image ( or any other pharo associated directory. )
2009/6/3 Mariano Martinez Peck <marianopeck@gmail.com>
It would be helpful if you attach debug.log. This file is located
in the
same directory where the image is.
Cheers,
Mariano
2009/6/3 Sean Allen <sean@monkeysnatchbanana.com>
that i dont really know how to describe... so i'm going to
attach a
screenshot... i opened the lastest pharo dev image... checked to see if the redraw bug that i have been experiencing was still there... went to quick and got a sudden flurry of message not understood errors ( see screenshot of the rearranged windows )... i wasnt able to reliably reproduce but, when doing the same thing ( open and quit... ) about 2 out of every five times i got message not understood windows popping up.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo- project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project_________... Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project