Hi, again.

Okay. Actually, you do need the event tickler for CMD+. if no other process
fetches events. Seems to be some VM-specific behavior you cannot trace at
Smalltalk level.

The CMD+. will not be recognized by the VM if there was no recent
EventSensor >> #fetchMoreEvents. Seems to be a side-effect.

So, no. We cannot get rid of the event tickler. However, why is there an
InterruptSemaphore if the event tickler could easily check for CMD+. itself?
Why involve the VM at all?

Best,
Marcel



--
View this message in context: http://forum.world.st/Discard-the-event-tickler-process-tp4888251p4888267.html
Sent from the Squeak - Dev mailing list archive at Nabble.com.