On Thu, Jun 4, 2009 at 3:11 AM, Michael Rueger <span dir="ltr">&lt;<a href="mailto:m.rueger@acm.org">m.rueger@acm.org</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">St�phane Ducasse wrote:<br>
&gt; Thanks.<br>
&gt;<br>
&gt; I think that for the MouseOverHandler it would be good to know if this<br>
&gt; is related to Sensor changes.<br>
&gt; Mike what you think?<br>
<br>
</div>It shouldn&#39;t. On the Morphic side there weren&#39;t any changes to process<br>
behavior, it still pulls the events out of the queue in the step cycle.<br>
<font color="#888888"><font class="Apple-style-span" color="#000000"><font class="Apple-style-span" color="#888888"></font></font></font></blockquote><div><br></div><div>Just as a bit more info. I used squeak for several months without ever seeing this error.</div>
<div>I used pharo for 3 months without seeing this error. I&#39;ve only gotten this error in the latest images</div><div>with the latest vm and get it constantly. Not occassionally, I can get this to happen at least</div>
<div>once every 120 seconds or so, sometimes more often. It would seem to be as an outsider,</div><div>that something must have changed.�</div></div>