qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierre d'Herbemont <stegefin@free.fr>
To: qemu-devel@nongnu.org, Mike Kronenberg <mike.kronenberg@kberg.ch>
Cc: Qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Experimental Cocoa Video Driver - Mousesupport and Keymap
Date: Fri,  8 Apr 2005 20:29:15 +0200	[thread overview]
Message-ID: <1112984955.4256cd7b8267f@imp6-q.free.fr> (raw)
In-Reply-To: <425439AA.5000509@kberg.ch>

Selon Mike Kronenberg <mike.kronenberg@kberg.ch>:

> Hello
>
> this patch provides initial Mouse- and better Keyboard support.
> There are still alot of things to do.

Thanks for the work Mike :)

> known Bugs and Workarounds:
>
> -  still no modifiers (help is apreciated)

in NSEvent there is a method called - (unsigned int)modifierFlags.

> -> no grab and ungrab (use alt-tab to switch)
>
> -  Mouseevents are only correcty passed, if the Cursor is within the
> qemu-Window, when it's activated (else the Mousedown/Mouseup are passed
> to the window, that was under the Cursor, when the qemu-Window is activated)

Probably polling for the event in NSEventTrackingRunLoopMode would help.

Also, I think your code should be cleaned up a bit. I think of all those
commented lines like:

@@ -253,16 +330,26 @@

     if (is_active_console(vga_console))
         vga_update_display();
+
+//    [NSCursor hide];
+//    CGAssociateMouseAndMouseCursorPosition ( FALSE );
+

which are not needed, and more confusing than really helpful. Also you define:

+
+static uint8_t modifiers_state[256]; //Mike
+

and you don't use it... I guess you should add this variable when the rest of
the code uses it.

Anyway, Keep up the good work.

Pierre.

PS: You should add the "[Patch]" keyword to the subject next time.

      reply	other threads:[~2005-04-08 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-06 19:34 [Qemu-devel] Experimental Cocoa Video Driver - Mousesupport and Keymap Mike Kronenberg
2005-04-08 18:29 ` Pierre d'Herbemont [this message]

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=1112984955.4256cd7b8267f@imp6-q.free.fr \
    --to=stegefin@free.fr \
    --cc=mike.kronenberg@kberg.ch \
    --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).