On 08/27/2014 04:15 AM, Pekka Paalanen wrote:
That describes the situation pretty closely, except the action is on
some subset of the wl_surfaces (for instance, only on the wl_surfaces
that belong to the client).
What I described in the quote above was just a meaningless chain of
abstract happ
On Wed, 20 Aug 2014 13:20:46 -0700
Bill Spitzak wrote:
> On 08/20/2014 12:13 PM, Pekka Paalanen wrote:
>
> > What would be a use case, where you might get blinking?
> >
> > If the
> > item is highlighted because an action with the input tool on any
> > wl_surface may affect it, why remove the h
On 08/20/2014 12:13 PM, Pekka Paalanen wrote:
What would be a use case, where you might get blinking?
> If the
item is highlighted because an action with the input tool on any
wl_surface may affect it, why remove the highlight when the input
tool leaves?
That describes the situation pretty
On Thu, 17 Jul 2014 15:58:17 -0400
Lyude wrote:
> On Thu, 2014-07-17 at 11:48 -0700, Bill Spitzak wrote:
> > On 07/13/2014 12:17 PM, Lyude wrote:
> >
> > > - proximity_out
> > > Sent whenever the tool leaves the proximity of the tablet or moves
> > > out of the client surface. When the
On Tue, Aug 05, 2014 at 06:18:00PM -0700, Jason Gerecke wrote:
> On Sat, Aug 2, 2014 at 12:31 PM, Lyude wrote:
> > I'm sorry I took so long to reply to this! I only just found this e-mail
> > while I was cleaning my inbox up.
> >
> > On Wed, 2014-07-30 at 17:33 -0700, Jason Gerecke wrote:
> >> On
On Sat, Aug 2, 2014 at 12:31 PM, Lyude wrote:
> I'm sorry I took so long to reply to this! I only just found this e-mail
> while I was cleaning my inbox up.
>
> On Wed, 2014-07-30 at 17:33 -0700, Jason Gerecke wrote:
>> On Tue, Jul 29, 2014 at 12:44 PM, Lyude wrote:
>> > I'm more then willing to
I'm sorry I took so long to reply to this! I only just found this e-mail
while I was cleaning my inbox up.
On Wed, 2014-07-30 at 17:33 -0700, Jason Gerecke wrote:
> On Tue, Jul 29, 2014 at 12:44 PM, Lyude wrote:
> > I'm more then willing to add something to get the resolution
> > information, it
On Tue, Jul 29, 2014 at 12:44 PM, Lyude wrote:
> I'm more then willing to add something to get the resolution
> information, it wouldn't be too difficult to implement. I think I'm
> missing or forgetting something here though; why wouldn't we be able to
> get an actual value in degrees from the no
I'm more then willing to add something to get the resolution
information, it wouldn't be too difficult to implement. I think I'm
missing or forgetting something here though; why wouldn't we be able to
get an actual value in degrees from the normalized values we're getting
from the compositor? The v
On Mon, Jul 28, 2014 at 10:54 AM, Bill Spitzak wrote:
> On 07/28/2014 09:41 AM, Jason Gerecke wrote:
>
>> Normalizing the data is fine, but the resolution data needs to be
>> available somewhere as well. The GTK+ API doesn't require anything
>> more than the former, but Qt requires that there be s
On 07/28/2014 09:41 AM, Jason Gerecke wrote:
Normalizing the data is fine, but the resolution data needs to be
available somewhere as well. The GTK+ API doesn't require anything
more than the former, but Qt requires that there be some way to turn
the normalized value into degrees. For libinput t
On Wed, Jul 16, 2014 at 5:08 PM, Lyude wrote:
> On Mon, 2014-07-14 at 13:25 -0700, Jason Gerecke wrote:
>> On Sun, Jul 13, 2014 at 12:17 PM, Lyude wrote:
>> >wl_tablet specifications
>> > Version 2
>> >
>> > General notes:
>> > - Many
On Thu, Jul 17, 2014 at 11:48:03AM -0700, Bill Spitzak wrote:
> On 07/13/2014 12:17 PM, Lyude wrote:
>
> > - proximity_out
> > Sent whenever the tool leaves the proximity of the tablet or moves
> > out of the client surface. When the tool goes out of proximity,
> > button rel
On 07/17/2014 12:58 PM, Lyude wrote:
On Thu, 2014-07-17 at 11:48 -0700, Bill Spitzak wrote:
A button count could definitely be added. But for clarification, are you
suggesting this somehow replace the frame event we have right now?
What I am trying to fix is the need for all the code modules
On Thu, 2014-07-17 at 11:48 -0700, Bill Spitzak wrote:
> On 07/13/2014 12:17 PM, Lyude wrote:
>
> > - proximity_out
> > Sent whenever the tool leaves the proximity of the tablet or moves
> > out of the client surface. When the tool goes out of proximity,
> > button release ev
On 07/13/2014 12:17 PM, Lyude wrote:
- proximity_out
Sent whenever the tool leaves the proximity of the tablet or moves
out of the client surface. When the tool goes out of proximity,
button release events are sent before the initial proximity_out
On Wed, Jul 16, 2014 at 08:08:29PM -0400, Lyude wrote:
> On Mon, 2014-07-14 at 13:25 -0700, Jason Gerecke wrote:
> > On Sun, Jul 13, 2014 at 12:17 PM, Lyude wrote:
> > >wl_tablet specifications
> > > Version 2
> > >
> > > General notes:
On Mon, 2014-07-14 at 13:25 -0700, Jason Gerecke wrote:
> On Sun, Jul 13, 2014 at 12:17 PM, Lyude wrote:
> >wl_tablet specifications
> > Version 2
> >
> > General notes:
> > - Many of the axis values in this are normalized to either 0-6
On Sun, Jul 13, 2014 at 12:17 PM, Lyude wrote:
>wl_tablet specifications
> Version 2
>
> General notes:
> - Many of the axis values in this are normalized to either 0-65535 or
> (-65535)-65535. I would leave the axis values as-is sinc
wl_tablet specifications
Version 2
General notes:
- Many of the axis values in this are normalized to either 0-65535 or
(-65535)-65535. I would leave the axis values as-is since libinput reports
them as doubles, but since we only hav
20 matches
Mail list logo
