On 3/20/20 12:47 PM, Thomas Hellström (VMware) wrote:
On 3/20/20 12:27 PM, Simon Ser wrote:
On Friday, March 20, 2020 11:59 AM, Thomas Hellström
wrote:
On 3/20/20 10:13 AM, Pekka Paalanen wrote:
It seems people are also forgetting the problem of associating the
cursor plane with an input d
On 3/20/20 12:27 PM, Simon Ser wrote:
On Friday, March 20, 2020 11:59 AM, Thomas Hellström
wrote:
On 3/20/20 10:13 AM, Pekka Paalanen wrote:
On Thu, 19 Mar 2020 23:57:09 +0100
Thomas Hellström (VMware) thomas...@shipmail.org wrote:
Hi,
On 3/19/20 10:07 PM, Simon Ser wrote:
Is that somet
On Friday, March 20, 2020 11:59 AM, Thomas Hellström
wrote:
> On 3/20/20 10:13 AM, Pekka Paalanen wrote:
>
> > On Thu, 19 Mar 2020 23:57:09 +0100
> > Thomas Hellström (VMware) thomas...@shipmail.org wrote:
> >
> > > Hi,
> > > On 3/19/20 10:07 PM, Simon Ser wrote:
> > >
> > > > > > > > Is that so
On 3/20/20 10:13 AM, Pekka Paalanen wrote:
On Thu, 19 Mar 2020 23:57:09 +0100
Thomas Hellström (VMware) wrote:
Hi,
On 3/19/20 10:07 PM, Simon Ser wrote:
Is that something that should be done?
If the hotspot property also had a "disabled" value, then Weston could
set the hotspot to disabled w
On Thu, 19 Mar 2020 23:57:09 +0100
Thomas Hellström (VMware) wrote:
> Hi,
>
> On 3/19/20 10:07 PM, Simon Ser wrote:
> > Is that something that should be done?
> > If the hotspot property also had a "disabled" value, then Weston could
> > set the hotspot to disabled when it is using t
Hi,
On 3/19/20 10:07 PM, Simon Ser wrote:
Is that something that should be done?
If the hotspot property also had a "disabled" value, then Weston could
set the hotspot to disabled when it is using the cursor plane for
non-cursor content and not lose the feature. And of course set hotspot
correct
> >>> Is that something that should be done?
> >>> If the hotspot property also had a "disabled" value, then Weston could
> >>> set the hotspot to disabled when it is using the cursor plane for
> >>> non-cursor content and not lose the feature. And of course set hotspot
> >>> correctly when it in f
Hi,
On 3/19/20 9:14 PM, Simon Ser wrote:
On Thursday, March 19, 2020 7:18 PM, Hans de Goede wrote:
The only way to fix that is to stop Weston from putting non-cursor
content on the cursor plane.
Correct.
Is that something that should be done?
If the hotspot property also had a "disabled"
On Thursday, March 19, 2020 7:18 PM, Hans de Goede wrote:
> > > > The only way to fix that is to stop Weston from putting non-cursor
> > > > content on the cursor plane.
> > >
> > > Correct.
> >
> > Is that something that should be done?
> > If the hotspot property also had a "disabled" value, th
Hi,
On 3/19/20 4:16 PM, Pekka Paalanen wrote:
On Thu, 19 Mar 2020 15:30:03 +0100
Hans de Goede wrote:
The only way to fix that is to stop Weston from putting non-cursor
content on the cursor plane.
Correct.
Is that something that should be done?
If the hotspot property also had a "dis
> >>> On Wed, 18 Mar 2020 15:28:02 +0100
> >>> Hans de Goede wrote:
> >>>
> >>>> ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> >>>> coordinates. Mutter (and Weston) have tried to emulate this by shi
Hi,
On 3/19/20 3:48 PM, Pekka Paalanen wrote:
On Thu, 19 Mar 2020 14:51:41 +0100
Michel Dänzer wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2020-03-19 1:54 p.m., Pekka Paalanen wrote:
On Thu, 19 Mar 2020 12:52:14 +0100 Hans de Goede
wrote:
On 3/19/20 12:35 PM, Michel Dänzer wro
On Thu, 19 Mar 2020 14:51:41 +0100
Michel Dänzer wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 2020-03-19 1:54 p.m., Pekka Paalanen wrote:
> > On Thu, 19 Mar 2020 12:52:14 +0100 Hans de Goede
> > wrote:
> >> On 3/19/20 12:35 PM, Michel Dänzer wrote:
> >>> On 2020-03-18 4:2
Hi,
On 3/19/20 1:58 PM, Pekka Paalanen wrote:
On Thu, 19 Mar 2020 12:49:27 +0100
Hans de Goede wrote:
Hi,
On 3/19/20 11:00 AM, Pekka Paalanen wrote:
On Wed, 18 Mar 2020 15:28:02 +0100
Hans de Goede wrote:
ATM the Atomic KMS API lacks the ability to set cursor hot-spot
coordinates
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2020-03-19 1:54 p.m., Pekka Paalanen wrote:
> On Thu, 19 Mar 2020 12:52:14 +0100 Hans de Goede
> wrote:
>> On 3/19/20 12:35 PM, Michel Dänzer wrote:
>>> On 2020-03-18 4:22 p.m., Simon Ser wrote:
>
> On 3/18/20 3:38 PM, Simon Ser wrote:
On 3/19/20 11:00 AM, Pekka Paalanen wrote:
> > >
> > > > On Wed, 18 Mar 2020 15:28:02 +0100
> > > > Hans de Goede hdego...@redhat.com wrote:
> > > >
> > > > > ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> > > > > coor
e:
> > >
> > >> ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> > >> coordinates. Mutter (and Weston) have tried to emulate this by shifting
> > >> the coordinates for where to draw the cursor by the hotspot-coordinates
> > >> an
On Thu, 19 Mar 2020 12:49:27 +0100
Hans de Goede wrote:
> Hi,
>
> On 3/19/20 11:00 AM, Pekka Paalanen wrote:
> > On Wed, 18 Mar 2020 15:28:02 +0100
> > Hans de Goede wrote:
> >
> >> ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> &
On Thu, 19 Mar 2020 12:52:14 +0100
Hans de Goede wrote:
> Hi,
>
> On 3/19/20 12:35 PM, Michel Dänzer wrote:
> > On 2020-03-18 4:22 p.m., Simon Ser wrote:
> >>>
> >>> On 3/18/20 3:38 PM, Simon Ser wrote:
>
> > 1) Letting the VM-viewer window-system draw the cursor as it normally
>
Hi,
On 3/19/20 12:35 PM, Michel Dänzer wrote:
On 2020-03-18 4:22 p.m., Simon Ser wrote:
On 3/18/20 3:38 PM, Simon Ser wrote:
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-surfac
Hi,
On 3/19/20 11:00 AM, Pekka Paalanen wrote:
On Wed, 18 Mar 2020 15:28:02 +0100
Hans de Goede wrote:
ATM the Atomic KMS API lacks the ability to set cursor hot-spot
coordinates. Mutter (and Weston) have tried to emulate this by shifting
the coordinates for where to draw the cursor by the
On 2020-03-18 4:22 p.m., Simon Ser wrote:
>>
>> On 3/18/20 3:38 PM, Simon Ser wrote:
>>>
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 c
On Wed, 18 Mar 2020 15:28:02 +0100
Hans de Goede wrote:
> ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> coordinates. Mutter (and Weston) have tried to emulate this by shifting
> the coordinates for where to draw the cursor by the hotspot-coordinates
> and always u
On Thursday, March 19, 2020 10:57 AM, Pekka Paalanen
wrote:
> On Wed, 18 Mar 2020 14:38:48 +
> Simon Ser cont...@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 t
On Wed, 18 Mar 2020 14:38:48 +
Simon Ser 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 g
Hi,
On 3/18/20 4:09 PM, Daniel Vetter wrote:
On Wed, Mar 18, 2020 at 3:29 PM Hans de Goede wrote:
Hi All,
I'm not sure if $subject was a conscious design decision, or an oversight,
but that does not really matter.
ATM the Atomic KMS API lacks the ability to set cursor hot-spot
coordi
> Hi,
>
> On 3/18/20 3:38 PM, Simon Ser 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
On Wed, Mar 18, 2020 at 3:29 PM Hans de Goede wrote:
>
> Hi All,
>
> I'm not sure if $subject was a conscious design decision, or an oversight,
> but that does not really matter.
>
> ATM the Atomic KMS API lacks the ability to set cursor hot-spot
> coordinates. Mutt
Hi,
On 3/18/20 3:38 PM, Simon Ser 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?
Because then moving
Hi,
On 3/18/20 3:28 PM, Hans de Goede wrote:
Hi All,
I'm not sure if $subject was a conscious design decision, or an oversight,
but that does not really matter.
ATM the Atomic KMS API lacks the ability to set cursor hot-spot
coordinates. Mutter (and Weston) have tried to emulate th
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 c
Hi All,
I'm not sure if $subject was a conscious design decision, or an oversight,
but that does not really matter.
ATM the Atomic KMS API lacks the ability to set cursor hot-spot
coordinates. Mutter (and Weston) have tried to emulate this by shifting
the coordinates for where to dra
32 matches
Mail list logo
