I meant a type of popup that stays up when the button is released. I
think in Wayland terms it is a child or transient-for window, not what
it is calling a "popup" in wl_shell.
This is a real problem and anybody who has written a popup menu system
would know about it.
I do think the problem
2014-07-02 1:55 GMT+03:00 Bill Spitzak :
>
>
> On 07/01/2014 12:35 PM, Jasper St. Pierre wrote:
>>
>> "A blink in the highlighting"?
>
>
> Yes. Say the client wants to highlight the button being pressed and it has
> popped up a menu, If the mouse is moved from the button to the menu, the
> client w
On 07/01/2014 04:06 PM, Jason Gerecke wrote:
yep, Lyude's latest protocol draft (in the works) does/will have that in it,
to have the built-in/display tablets not use a cursor, the external ones
have a cursor. we haven't really worried about the client-drawing area mode
yet because it'll likely
On Mon, Jun 30, 2014 at 3:46 AM, Peter Hutterer
wrote:
> On 30/06/2014 20:23 , Pekka Paalanen wrote:
>>
>> On Mon, 30 Jun 2014 09:33:15 +0300
>> Pekka Paalanen wrote:
>>
>>> On Mon, 30 Jun 2014 11:08:35 +1000
>>> Peter Hutterer wrote:
>>>
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paal
On 07/01/2014 12:35 PM, Jasper St. Pierre wrote:
"A blink in the highlighting"?
Yes. Say the client wants to highlight the button being pressed and it
has popped up a menu, If the mouse is moved from the button to the menu,
the client wants to keep the button highlighted.
If in fact the s
"A blink in the highlighting"?
On Tue, Jul 1, 2014 at 3:32 PM, Bill Spitzak wrote:
> On 06/30/2014 09:50 PM, Peter Hutterer wrote:
>
> Yes this makes sense. Sorry I was confusing it with the X implementation
>>> where the Enter event replaced a Move event.
>>>
>>
>> it does? it's actually one
On 06/30/2014 09:50 PM, Peter Hutterer wrote:
Yes this makes sense. Sorry I was confusing it with the X implementation
where the Enter event replaced a Move event.
it does? it's actually one of the ambiguous parts of the X protocol.
nothing prevents you from sending motion events for the same
On Mon, Jun 30, 2014 at 06:55:25PM -0700, Bill Spitzak wrote:
> On 06/30/2014 12:46 AM, Pekka Paalanen wrote:
>
> >>I was assuming the enter event contains enough information to know which
> >>device is causing it.
> >
> >It is the wl_pointer of a specific wl_seat:
> >http://people.collabora.com/~
On 06/30/2014 12:46 AM, Pekka Paalanen wrote:
I was assuming the enter event contains enough information to know which
device is causing it.
It is the wl_pointer of a specific wl_seat:
http://people.collabora.com/~jonny/protocol/wl_pointer.html#Event:enter
No information about the actual phys
On Mon, 30 Jun 2014 20:46:46 +1000
Peter Hutterer wrote:
> On 30/06/2014 20:23 , Pekka Paalanen wrote:
> > On Mon, 30 Jun 2014 09:33:15 +0300
> > Pekka Paalanen wrote:
> >
> > If you have a tabletscreen, and your tool is a set of fingers, is it
> > any different to a touchscreen? Could we even c
On 30/06/2014 20:23 , Pekka Paalanen wrote:
On Mon, 30 Jun 2014 09:33:15 +0300
Pekka Paalanen wrote:
On Mon, 30 Jun 2014 11:08:35 +1000
Peter Hutterer wrote:
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
On Fri, 27 Jun 2014 13:04:59 -0700
Bill Spitzak wrote:
On 06/26/2
On 30/06/2014 16:33 , Pekka Paalanen wrote:
On Mon, 30 Jun 2014 11:08:35 +1000
Peter Hutterer wrote:
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
On Fri, 27 Jun 2014 13:04:59 -0700
Bill Spitzak wrote:
[...]
- The pen moves the seat's mouse cursor, always. If more than
On Mon, 30 Jun 2014 09:33:15 +0300
Pekka Paalanen wrote:
> On Mon, 30 Jun 2014 11:08:35 +1000
> Peter Hutterer wrote:
>
> > On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
> > > On Fri, 27 Jun 2014 13:04:59 -0700
> > > Bill Spitzak wrote:
> > >
> > > > On 06/26/2014 09:38 PM,
On Sun, 29 Jun 2014 23:43:21 -0700
Bill Spitzak wrote:
> On 06/29/2014 11:33 PM, Pekka Paalanen wrote:
>
> >> moving the visible cursor doesn't necessarily mean that it must translate
> >> into the wl_pointer protocol. It's probably awkward at first if the pointer
> >> moves and clients don't re
On 06/29/2014 11:33 PM, Pekka Paalanen wrote:
moving the visible cursor doesn't necessarily mean that it must translate
into the wl_pointer protocol. It's probably awkward at first if the pointer
moves and clients don't react to it but if we essentially require the
toolkits to support wl_tablet
On 06/28/2014 02:41 AM, Pekka Paalanen wrote:
- The pen moves the seat's mouse cursor, always. If more than one cursor
is wanted the pen should be in a different seat. The user is not
manipulating more than one device at a time and does not want to see two
cursors.
...and then you said the exa
On Mon, 30 Jun 2014 11:08:35 +1000
Peter Hutterer wrote:
> On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
> > On Fri, 27 Jun 2014 13:04:59 -0700
> > Bill Spitzak wrote:
> >
> > > On 06/26/2014 09:38 PM, Ping Cheng wrote:
> > >
> > > > With my experience, mapping whole tablet t
On Sat, Jun 28, 2014 at 12:41:33PM +0300, Pekka Paalanen wrote:
> On Fri, 27 Jun 2014 13:04:59 -0700
> Bill Spitzak wrote:
>
> > On 06/26/2014 09:38 PM, Ping Cheng wrote:
> >
> > > With my experience, mapping whole tablet to a window or a
> > > specific display area is preferred. That is how map
On Fri, 27 Jun 2014 13:04:59 -0700
Bill Spitzak wrote:
> On 06/26/2014 09:38 PM, Ping Cheng wrote:
>
> > With my experience, mapping whole tablet to a window or a
> > specific display area is preferred. That is how mapping works on Windows
> > and Mac too.
>
> First this is *only* when the draw
On 06/26/2014 09:38 PM, Ping Cheng wrote:
With my experience, mapping whole tablet to a window or a
specific display area is preferred. That is how mapping works on Windows
and Mac too.
First this is *only* when the drawing program wants it to happen. There
is some kind of mode switch so the
On Thu, 26 Jun 2014 18:45:07 -0700
Jason Gerecke wrote:
> On Thu, Jun 26, 2014 at 12:12 AM, Peter Hutterer
> wrote:
> > On Thu, Jun 26, 2014 at 09:48:37AM +0300, Pekka Paalanen wrote:
> >> Hi,
> >>
> >> it seems you forgot to reply-to-all, so I have re-added everyone and
> >> not trimmed the quo
On Thursday, June 26, 2014, Peter Hutterer wrote:
> On Thu, Jun 26, 2014 at 09:48:37AM +0300, Pekka Paalanen wrote:
> > Hi,
> >
> > it seems you forgot to reply-to-all, so I have re-added everyone and
> > not trimmed the quotation.
> >
> > On Wed, 25 Jun 2014 18:37:08 -0400
> > Lyude > wrote:
> >
On Thu, Jun 26, 2014 at 12:12 AM, Peter Hutterer
wrote:
> On Thu, Jun 26, 2014 at 09:48:37AM +0300, Pekka Paalanen wrote:
>> Hi,
>>
>> it seems you forgot to reply-to-all, so I have re-added everyone and
>> not trimmed the quotation.
>>
>> On Wed, 25 Jun 2014 18:37:08 -0400
>> Lyude wrote:
>>
>>
On Thu, Jun 26, 2014 at 09:48:37AM +0300, Pekka Paalanen wrote:
> Hi,
>
> it seems you forgot to reply-to-all, so I have re-added everyone and
> not trimmed the quotation.
>
> On Wed, 25 Jun 2014 18:37:08 -0400
> Lyude wrote:
>
> > On Wed, 2014-06-25 at 15:19 +0300, Pekka Paalanen wrote:
> > >
On Thu, Jun 26, 2014 at 09:23:51AM +0300, Pekka Paalanen wrote:
> On Thu, 26 Jun 2014 14:14:33 +1000
> Peter Hutterer wrote:
[...]
> > > >good point, thanks!
> > > >>> - Name: time
> > > >>> Type: uint
> > > >>> The time of the event with millisecond granularity.
> >
Hi,
it seems you forgot to reply-to-all, so I have re-added everyone and
not trimmed the quotation.
On Wed, 25 Jun 2014 18:37:08 -0400
Lyude wrote:
> On Wed, 2014-06-25 at 15:19 +0300, Pekka Paalanen wrote:
> > On Tue, 24 Jun 2014 21:56:09 -0400
> > Chandler Paul wrote:
> >
> > > Hello! As yo
On Thu, 26 Jun 2014 14:14:33 +1000
Peter Hutterer wrote:
> On Wed, Jun 25, 2014 at 08:22:21PM -0700, Jason Ekstrand wrote:
> >
> > On 06/25/2014 06:05 PM, Peter Hutterer wrote:
> > >On Wed, Jun 25, 2014 at 03:19:02PM +0300, Pekka Paalanen wrote:
> > >>On Tue, 24 Jun 2014 21:56:09 -0400
> > >>Cha
On Wed, Jun 25, 2014 at 08:22:21PM -0700, Jason Ekstrand wrote:
>
> On 06/25/2014 06:05 PM, Peter Hutterer wrote:
> >On Wed, Jun 25, 2014 at 03:19:02PM +0300, Pekka Paalanen wrote:
> >>On Tue, 24 Jun 2014 21:56:09 -0400
> >>Chandler Paul wrote:
> >>
> >>>Hello! As you all know I've been working o
On 06/25/2014 06:05 PM, Peter Hutterer wrote:
On Wed, Jun 25, 2014 at 03:19:02PM +0300, Pekka Paalanen wrote:
On Tue, 24 Jun 2014 21:56:09 -0400
Chandler Paul wrote:
Hello! As you all know I've been working on adding drawing tablet
support to the Wayland protocol. Now that we've added suppor
On Wed, Jun 25, 2014 at 03:19:02PM +0300, Pekka Paalanen wrote:
> On Tue, 24 Jun 2014 21:56:09 -0400
> Chandler Paul wrote:
>
> > Hello! As you all know I've been working on adding drawing tablet
> > support to the Wayland protocol. Now that we've added support for
> > tablets to libinput, the ne
On Tue, 24 Jun 2014 21:56:09 -0400
Chandler Paul wrote:
> Hello! As you all know I've been working on adding drawing tablet
> support to the Wayland protocol. Now that we've added support for
> tablets to libinput, the next step is writing the actual protocol that
> will be implemented by the com
Hello! As you all know I've been working on adding drawing tablet
support to the Wayland protocol. Now that we've added support for
tablets to libinput, the next step is writing the actual protocol that
will be implemented by the compositor. Following this blurb is the
current draft of the tablet p
32 matches
Mail list logo
