From: Pekka Paalanen <ppaalanen@gmail.com>
To: Simon Ser <contact@emersion.fr>
Cc: "Hans de Goede" <hdegoede@redhat.com>,
"Jonas Ådahl" <jadahl@redhat.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: Atomic KMS API lacks the ability to set cursor hot-spot coordinates
Date: Thu, 19 Mar 2020 11:57:48 +0200 [thread overview]
Message-ID: <20200319115748.276d8f32@eldfell.localdomain> (raw)
In-Reply-To: <ADrBkiVj05c2ZYEz46BNJrrChY-PCxme8HOeHHGOLjIR5XpBZoyIY5aUnSfXCm0wrYr0-Iuh80vnZqmRQ_jZaslv2Q2P7N6q5yCG0AeWovU=@emersion.fr>
[-- Attachment #1.1: Type: text/plain, Size: 688 bytes --]
On Wed, 18 Mar 2020 14:38:48 +0000
Simon Ser <contact@emersion.fr> wrote:
> Hi,
>
> > 1) Letting the VM-viewer window-system draw the cursor as it normally
> > would draw it.
>
> Why is this important? Can't the VM viewer hide the cursor and use a
> sub-surface to manually draw the cursor plane configured by the guest?
>
> This would also allow the compositor running inside the VM to correctly
> have control over the cursor position, which is necessary for pointer
> constraints.
Aren't pointer motion events delivered in absolute and not relative
coordinates in the "seamless mode"?
Do we do pointer constraints also with absolute motion?
Thanks,
pq
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-03-19 9:58 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 14:28 Atomic KMS API lacks the ability to set cursor hot-spot coordinates Hans de Goede
2020-03-18 14:38 ` Simon Ser
2020-03-18 15:04 ` Hans de Goede
2020-03-18 15:22 ` Simon Ser
2020-03-19 11:35 ` Michel Dänzer
2020-03-19 11:52 ` Hans de Goede
2020-03-19 12:54 ` Pekka Paalanen
2020-03-19 13:51 ` Michel Dänzer
2020-03-19 14:48 ` Pekka Paalanen
2020-03-19 15:01 ` Hans de Goede
2020-03-19 9:57 ` Pekka Paalanen [this message]
2020-03-19 10:00 ` Simon Ser
2020-03-18 14:39 ` Hans de Goede
2020-03-18 15:09 ` Daniel Vetter
2020-03-18 22:20 ` Hans de Goede
2020-03-19 10:00 ` Pekka Paalanen
2020-03-19 11:49 ` Hans de Goede
2020-03-19 12:58 ` Pekka Paalanen
2020-03-19 13:16 ` Daniel Vetter
2020-03-19 13:24 ` Simon Ser
2020-03-19 14:30 ` Hans de Goede
2020-03-19 15:16 ` Pekka Paalanen
2020-03-19 18:18 ` Hans de Goede
2020-03-19 20:14 ` Simon Ser
2020-03-19 20:49 ` Hans de Goede
2020-03-19 21:07 ` Simon Ser
2020-03-19 22:57 ` Thomas Hellström (VMware)
2020-03-20 9:13 ` Pekka Paalanen
2020-03-20 10:59 ` Thomas Hellström (VMware)
2020-03-20 11:27 ` Simon Ser
2020-03-20 11:47 ` Thomas Hellström (VMware)
2020-03-21 8:56 ` Thomas Hellström (VMware)
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=20200319115748.276d8f32@eldfell.localdomain \
--to=ppaalanen@gmail.com \
--cc=contact@emersion.fr \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jadahl@redhat.com \
/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