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
