From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Porter-Duff alpha blending
Date: Mon, 9 Mar 2009 11:40:40 -0500 [thread overview]
Message-ID: <6F576360-490B-4471-A2A3-290E7270EFA2@corpus-callosum.com> (raw)
In-Reply-To: <bb9aee10903090828n5c5f6b3che6558ce1cb68391a@mail.gmail.com>
On Mar 9, 2009, at 10:28 AM, Michaelian Ennis wrote:
> I am confused as to why one would return eventNotHandledErr after
> handling the event?
Because it's not really handling the event. It just happens to be
the only hook available for monitoring the application event loop
(in this case: the dance between the Carbon Event Manager and p9p)
that I've found to force memscreen's image to flush. We still want
OS X's application event loop to do whatever it does to get the
window server and responder chain back--without messing up the
buffering that could cause a flicker when moving the window later.
-jas
next prev parent reply other threads:[~2009-03-09 16:40 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 21:32 erik quanstrom
2009-03-04 21:37 ` andrey mirtchovski
2009-03-04 21:42 ` andrey mirtchovski
2009-03-04 21:44 ` erik quanstrom
2009-03-04 21:53 ` andrey mirtchovski
2009-03-04 22:03 ` erik quanstrom
2009-03-04 22:21 ` andrey mirtchovski
2009-03-04 22:22 ` Devon H. O'Dell
2009-03-04 22:45 ` andrey mirtchovski
2009-03-04 22:59 ` erik quanstrom
2009-03-04 23:05 ` andrey mirtchovski
2009-03-04 23:58 ` Charles Forsyth
2009-03-05 1:04 ` erik quanstrom
2009-03-05 1:29 ` andrey mirtchovski
2009-03-05 2:07 ` andrey mirtchovski
2009-03-05 2:22 ` erik quanstrom
2009-03-06 3:21 ` andrey mirtchovski
2009-03-06 20:48 ` Russ Cox
2009-03-06 21:42 ` andrey mirtchovski
2009-03-08 22:33 ` Jeff Sickel
2009-03-09 15:28 ` Michaelian Ennis
2009-03-09 16:40 ` Jeff Sickel [this message]
2009-03-09 14:00 ` erik quanstrom
2009-03-09 15:32 ` yy
2009-03-04 21:53 erik quanstrom
2009-03-04 22:01 ` andrey mirtchovski
2009-03-05 18:31 maht
2009-03-04 21:18 ` andrey mirtchovski
2009-03-04 23:24 ` Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6F576360-490B-4471-A2A3-290E7270EFA2@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).