From: James Hogan <james@albanarts.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Cursor hidden with emulated touchscreen
Date: Thu, 17 May 2012 23:44:10 +0100 [thread overview]
Message-ID: <20120517224409.GA18682@balrog.le.imgtec.org> (raw)
Hi,
Since updating to QEMU v1.0 I've had a problem with automatic mouse
grab. Whenever I move the mouse over the QEMU window it seems to make
the mouse cursor invisible, but the input device being emulated is a
touchscreen providing absolute coordinates so the software in the
emulator doesn't provide a cursor either. This makes it somewhat hard to
know where I am clicking.
I can get the cursor to stop disappearing by commenting out
SDL_SetCursor(sdl_cursor_hidden);
in sdl_hide_cursor() in ui/sdl.c, but I suspect there's something else
wrong for this to be happening.
The touchscreen hardware is set up with qemu_add_mouse_event_handler()
with argument "absolute" set to 1.
Does anybody have any idea whether this is expected behaviour for
emulated touchscreens, and if not what I might be doing wrong to cause
the cursor to disappear?
Thanks
James
reply other threads:[~2012-05-17 22:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20120517224409.GA18682@balrog.le.imgtec.org \
--to=james@albanarts.com \
--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).