[Pharo-project] InputEventFetcher starving all other processes
pharo at stefan-marr.de
Sun Oct 31 16:56:10 EDT 2010
On 31 Oct 2010, at 19:15, Stefan Marr wrote:
> But the symptoms are that InputEventFetcher>>primGetNextEvent: delivers 500-1000x more events than EventSensor>>primGetNextEvent: in MVC or Squeak 4.1 images deliver.
Turns out that the array which is supposed to be filled in by '>>primGetNextEvent: array' does not get filled in correctly.
For some reason the old values stay in the array when there isn't any new event.
However, the very same code works for the non-Pharo images.
Was there any change to the code in or related to this primitive (<primitive: 94>) lately?
Software Languages Lab
Vrije Universiteit Brussel
Pleinlaan 2 / B-1050 Brussels / Belgium
Phone: +32 2 629 2974
Fax: +32 2 629 3525
More information about the Pharo-dev