On May-25, Dan Sugalski wrote:
> At 10:31 AM +0200 5/25/04, Leopold Toetsch wrote:
> >Dan Sugalski <[EMAIL PROTECTED]> wrote:
> >> An unsolicited event, on the other hand, is one that parrot generates
> >> as the result of something happening external to itself, or as the
> >> result of some recurr
At 12:26 PM -0400 5/27/04, Gordon Henriksen wrote:
Dan Sugalski wrote:
Gordon Henriksen wrote:
> So, for GUI events, could calling into parrot and doing the
> following from the OS event handler work to synchronously dispatch
> an event?
>
> ... parrot-ify a mouse-moved event into $P5 ...
Dan Sugalski wrote:
> Gordon Henriksen wrote:
>
> > So, for GUI events, could calling into parrot and doing the
> > following from the OS event handler work to synchronously dispatch
> > an event?
> >
> > ... parrot-ify a mouse-moved event into $P5 ...
> > post $P5
> > checkevent
>
At 11:29 PM -0400 5/26/04, Gordon Henriksen wrote:
On May 24, 2004, at 15.20, Dan Sugalski wrote:
Event Ops
=
The opcodes in this section are a combination of event requests and
event handling ops. It doesn't include the IO ops--those are
separate.
Most of the event request ops have two
On May 24, 2004, at 15.20, Dan Sugalski wrote:
Event Ops
=
The opcodes in this section are a combination of event requests and
event handling ops. It doesn't include the IO ops--those are separate.
Most of the event request ops have two forms, one of which takes a
callback PMC and user d
At 8:09 PM -0400 5/24/04, Uri Guttman wrote:
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> Parrot has a unified event and IO system--indeed events are nothing
DS> but satisfied IO requests. (Or, alternately, IO requests are nothing
DS> but solicited events with external data)
th
At 10:31 AM +0200 5/25/04, Leopold Toetsch wrote:
Dan Sugalski <[EMAIL PROTECTED]> wrote:
An unsolicited event, on the other hand, is one that parrot generates
as the result of something happening external to itself, or as the
result of some recurring event happening. Signals and GUI events, for
Dan Sugalski <[EMAIL PROTECTED]> wrote:
> An unsolicited event, on the other hand, is one that parrot generates
> as the result of something happening external to itself, or as the
> result of some recurring event happening. Signals and GUI events, for
> example, are unsolicted as are recurring tim
> "DS" == Dan Sugalski <[EMAIL PROTECTED]> writes:
DS> Events and IO
DS> =
DS> Parrot has a unified event and IO system--indeed events are nothing
DS> but satisfied IO requests. (Or, alternately, IO requests are nothing
DS> but solicited events with external data)
that
