When we switch away from our custom event handling, we still want to
be able to have first go at any events our application receives,
because in full-screen mode we want to send key events to the guest,
even if they would be menu item activation events. There are several
ways we could do that, but one simple approach is to subclass
NSApplication so we can implement a custom sendEvent method.
Do that, but for the moment have our sendEvent just invoke the
superclass method.
Signed-off-by: Peter Maydell <peter.mayd...@linaro.org>
Reviewed-by: BALATON Zoltan <bala...@eik.bme.hu>
Reviewed-by: Roman Bolshakov <r.bolsha...@yadro.com>
Tested-by: Roman Bolshakov <r.bolsha...@yadro.com>
Message-id: 20190214102816.3393-7-peter.mayd...@linaro.org
---
ui/cocoa.m | 13 ++++++++++++-
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/ui/cocoa.m b/ui/cocoa.m
index 1b54d42aba..00e3db69c9 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -1482,6 +1482,17 @@ - (void)adjustSpeed:(id)sender
@end
+@interface QemuApplication : NSApplication
+@end
+
+@implementation QemuApplication
+- (void)sendEvent:(NSEvent *)event
+{
+ COCOA_DEBUG("QemuApplication: sendEvent\n");
+ [super sendEvent: event];
+}
+@end
+
static void create_initial_menus(void)
{
// Add menus
@@ -1695,7 +1706,7 @@ int main (int argc, const char * argv[]) {
ProcessSerialNumber psn = { 0, kCurrentProcess };
TransformProcessType(&psn, kProcessTransformToForegroundApplication);
- [NSApplication sharedApplication];
+ [QemuApplication sharedApplication];
create_initial_menus();
--
2.17.2 (Apple Git-113)
