qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <andreas.faerber@web.de>
To: qemu-devel@nongnu.org
Cc: "Andreas Färber" <andreas.faerber@web.de>
Subject: [Qemu-devel] [PATCH 09/10] cocoa: Avoid warning related to multiple handleEvent: definitions
Date: Tue, 14 Jun 2011 03:22:06 +0200	[thread overview]
Message-ID: <1308014527-60251-10-git-send-email-andreas.faerber@web.de> (raw)
In-Reply-To: <1308014527-60251-9-git-send-email-andreas.faerber@web.de>

Avoid compiler confusion as to which method signature to use for the
handleEvent: selector on OSX >= 10.6 by making the variable type-safe
as opposed to generic 'id' type.
Requires moving the variable definition to after the class definition.

----8<----
ui/cocoa.m: In function ‘cocoa_refresh’:
ui/cocoa.m:997: warning: multiple methods named ‘-handleEvent:’ found
/System/Library/Frameworks/AppKit.framework/Headers/NSTextInputContext.h:84: warning: using ‘-(BOOL)handleEvent:(NSEvent *)theEvent’
ui/cocoa.m:272: warning: also found ‘-(void)handleEvent:(NSEvent *)event’
----8<---

Reported-by: Alexandre Raymond <cerbere@gmail.com>
Signed-off-by: Andreas Färber <andreas.faerber@web.de>
Tested-by: Alexandre Raymond <cerbere@gmail.com>
---
 ui/cocoa.m |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/ui/cocoa.m b/ui/cocoa.m
index 1c54759..515e684 100644
--- a/ui/cocoa.m
+++ b/ui/cocoa.m
@@ -63,7 +63,6 @@ typedef struct {
 } QEMUScreen;
 
 NSWindow *normalWindow;
-id cocoaView;
 static DisplayChangeListener *dcl;
 
 int gArgc;
@@ -278,6 +277,8 @@ static int cocoa_keycode_to_qemu(int keycode)
 - (QEMUScreen) gscreen;
 @end
 
+QemuCocoaView *cocoaView;
+
 @implementation QemuCocoaView
 - (id)initWithFrame:(NSRect)frameRect
 {
-- 
1.7.5.3

  reply	other threads:[~2011-06-14  1:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14  1:21 [Qemu-devel] [PULL 00/10] Fixes for Cocoa backend Andreas Färber
2011-06-14  1:21 ` [Qemu-devel] [PATCH 01/10] cocoa: do not create a spurious window for -version Andreas Färber
2011-06-14  1:21   ` [Qemu-devel] [PATCH 02/10] Fix compilation warning due to incorrectly specified type Andreas Färber
2011-06-14  1:22     ` [Qemu-devel] [PATCH 03/10] Cocoa: avoid displaying window when command-line contains '-h' or '-help' Andreas Färber
2011-06-14  1:22       ` [Qemu-devel] [PATCH 04/10] Remove warning in printf due to type mismatch Andreas Färber
2011-06-14  1:22         ` [Qemu-devel] [PATCH 05/10] configure: Fix check for fdatasync() Andreas Färber
2011-06-14  1:22           ` [Qemu-devel] [PATCH 06/10] Fix libfdt warnings on Darwin Andreas Färber
2011-06-14  1:22             ` [Qemu-devel] [PATCH 07/10] cocoa: Provide central qemu_main() prototype Andreas Färber
2011-06-14  1:22               ` [Qemu-devel] [PATCH 08/10] cocoa: Revert dependency on VNC Andreas Färber
2011-06-14  1:22                 ` Andreas Färber [this message]
2011-06-14  1:22                   ` [Qemu-devel] [PATCH 10/10] Darwin: Fix compilation warning regarding the deprecated daemon() function Andreas Färber
2011-06-27 14:48                 ` [Qemu-devel] [PATCH 08/10] cocoa: Revert dependency on VNC Jes Sorensen
2011-06-15 19:31 ` [Qemu-devel] [PULL 00/10] Fixes for Cocoa backend Blue Swirl

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=1308014527-60251-10-git-send-email-andreas.faerber@web.de \
    --to=andreas.faerber@web.de \
    --cc=qemu-devel@nongnu.org \
    /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).