Apple docs said that NSWindow -discardEventsMatchingMask:beforeEvent:
should just forward to NSApp
but a note on NSApplication -discardEventsMatchingMask:beforeEvent: states
"Typically, you send this message to an NSWindow object, rather than
to the application object. Discarding events for a window clears out
all of the events for that window only, leaving events for other
windows in place."
out implementation in NSWindow is like
- (void) discardEventsMatchingMask: (unsigned int)mask
beforeEvent: (NSEvent*)lastEvent
{
[NSApp discardEventsMatchingMask: mask beforeEvent: lastEvent];
}
wouldn't that mask the events off all windows?
What would be bad if we store all the events from server queue on a
queue on NSApplication (so we don't need to fix op for server ?) and
let the display server directly postEvent:atStart: to the app.
Beside that it would allow applications to manipulate the event queue
directly, like custom event flood filtering, I think that would ease
the work on multiple input devices/points implementation in future as
well.
For the point of filtering, I am concerned of the point that tons
unused NSEvents would be discarded anyway but I don't think it's
backend's decision to decide what application developer would want.
Thanks
Banlu Kemiyatorn
--
.----. Banlu Kemiyatorn
/.../\...\ 漫画家
|.../ \...| http://qstx.blogspot.com (Free Software Advocacy & Development)
|../ \..| http://feedbat.blogspot.com (Studio Work For Hire)
\/ \/ http://groundzerostudiocomplex.blogspot.com (Studio Research)
_______________________________________________
Gnustep-dev mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/gnustep-dev
