open to the same VM/guest instance? Will they fight
over controlling the same pointer?
I can't speak for all consoles, but VMware at least uses a bunch of
heuristics that typically boil down to which mouse input source has been
moving the cursor most recently.
--Michael Banack
ccelerate it all the way through the
client and send absolute input events down.
--Michael Banack
On 7/4/23 01:08, Pekka Paalanen wrote:
On Mon, 3 Jul 2023 14:06:56 -0700
Michael Banack wrote:
Hi, I can speak to the virtual mouse/console half of this from the
VMware-side.
I believe Zack's preparing a new set of comments here that can speak to
most of your concerns, but I'
On 7/6/23 01:01, Pekka Paalanen wrote:
On Wed, 5 Jul 2023 09:08:07 -0700
Michael Banack wrote:
On 7/4/23 01:08, Pekka Paalanen wrote:
On Mon, 3 Jul 2023 14:06:56 -0700
Michael Banack wrote:
Hi, I can speak to the virtual mouse/console half of this from the
VMware-side.
I believe
s the graphics part
correctly but does something just weird enough on the input side to not
be considered compliant.
So I guess I would vote for trying to include something to that effect
as context or explanation, but not try to strictly define how that works?
--Michael Banack
On 7/10/23 01:17, Pekka Paalanen wrote:
On Fri, 7 Jul 2023 13:54:21 -0700
Michael Banack wrote:
On 7/7/23 01:38, Pekka Paalanen wrote:
...
The question of which input device corresponds to which cursor plane
might be good to answer too. I presume the VM runner is configured to
expose
Yes, that patch should be:
Signed-off-by: Michael Banack
--Michael Banack
On 10/23/23 14:29, Javier Martinez Canillas wrote:
Albert Esteve writes:
From: Michael Banack
To clarify the intent and reasoning behind the hotspot properties
introduce userspace documentation that goes over
