On Sun, Feb 03, 2013 at 07:57:11PM +0000, H. Hirzel wrote:
> Dave
> 
> I assume you commented out
>    self wait2ms.
> in
>    EventSensor >> primKbdPeek
> and
>    EventSensoer >> primKbdNext
> 

I just commented out the body of the wait2ms method, so effectively
like removing it entirely from the system.

> this indeed has the effect that the cursor is no positioned correctly
> in MVC when typing fast in an MVC workspace.
> 
> What could be the possible side effect of removing the call to
>      self wait2ms
> 
> in these two methods?
> 

I don't know. I guess I would want to go back and understand the original
motivation for adding it. A lot a things have changed since 2005, and I
would not want to do a quick fix without understanding it. But for now
I'll leave it commented out in my own image :)

> --Hannes
> 
> 
> On 2/3/13, David T. Lewis <lewis at mail.msen.com> wrote:
> > On Sun, Feb 03, 2013 at 10:33:14AM +0100, St??phane Rollandin wrote:
> >> Also I found this on the web:
> >> http://forum.world.st/Real-Slowdown-of-InputSensor-between-3-8-and-3-9-td62714.html
> >>
> >> from where it seems that the reason for the wait is related to system
> >> window panes resizing logic...
> >
> > Stef,
> >
> > Wow, you just found the cause of our badly broken keyboard entry in MVC :)
> >
> > Since about Squeak 3.9, keyboard entry (especially on Linux) has had an
> > odd latency delay that makes it all but unusable. I just tried commenting
> > out the wait2ms, and suddenly keyboard entry is working again. I see no
> > immediately obvious ill effects (cpu use does not go too high, and things
> > generally still work fine).
> >
> > It seems that the delay was added back in about 2005, and very likely
> > the changes to input events in the Squeak 3.9 time frame caused it to
> > become a problem. I'm not sure the right way to fix this, but at least
> > now we know the source of the problem.
> >
> > Thanks!
> >
> > Dave
> >
> >
> >