[ENH] OS-level events

David Harris dpharris at bc.sympatico.ca
Sat Jul 3 19:21:15 UTC 1999


> Peter William Lount wrote:
>
> > Hi Peter,
> >
> > One difference with keyboard and mouse events it is that in the general
> > case the "ACTIVE" window consumes them while the other windows ignore them
> > unless the event is a one (like a button down event in an inactive window)
> > ...
> > abstraction and reuse a lot of the code, or is this just wishful thinking
> > on
> > my part?
> >
> > Peter
> >
> > From: Reinier van Loon <R.L.J.M.W.van.Loon at inter.nl.net>
> > To: squeak at cs.uiuc.edu <squeak at cs.uiuc.edu>
> > Date: Thursday, July 01, 1999 6:06 AM
> > Subject: Re: [ENH] OS-level events
> >
> > >I keep getting the impression that the event systems designed so far are
> > >only concerned with keyboard or mouse events. These events are then put in
> > >an event queue with some information regarding the event.
> > >
> > >Why not define an event as <time, object> and event queue as a collection
> > >sorted by time?
> > >The global event (interrupt) handler detects an event on the queue (tim's
> > >work) and gets the rest of the event of the object mentioned in the event.
> > >
> > >In this way, each object (keyboard, mouse, network, etc.) can have it's
> > own
> > >buffer.
> > >And composite events are detected easily by comparing the time stamps.
> > >
> > >You could even start new processes to deal with events or have different
> > >event handlers wait on the queues of the objects. No 'centralized' event
> > >queue anymore.
> > >
> > >Just an idea.
> > >
> > >Reinier.
> > >
> > >

  A small two-bits:

NeWS (Network extensible Windows System -(Java in Display Postscript?) from Sun
had an extensive events distribution system.

David





More information about the Squeak-dev mailing list