My primary complaint is that "X" and "Y" are both translational axes,
and by analogy "Z" should be as well. Using it as the name for a
rotational axis just muddies things, especially when we already have
"DISTANCE". My second complaint is the same as Peter's: it should be
clear that is axis is in t
On 12/08/2014 06:59 PM, Peter Hutterer wrote:
On Mon, Dec 08, 2014 at 06:49:37PM -0800, Bill Spitzak wrote:
On 12/08/2014 06:37 PM, Peter Hutterer wrote:
On Mon, Dec 08, 2014 at 11:03:58AM -0800, Bill Spitzak wrote:
Shouldn't this use the same api as the input methods, since it is in fact
On Mon, Dec 08, 2014 at 06:49:37PM -0800, Bill Spitzak wrote:
>
>
> On 12/08/2014 06:37 PM, Peter Hutterer wrote:
> >On Mon, Dec 08, 2014 at 11:03:58AM -0800, Bill Spitzak wrote:
> >>Shouldn't this use the same api as the input methods, since it is in fact an
> >>input method?
> >
> >please expla
On 12/08/2014 06:37 PM, Peter Hutterer wrote:
On Mon, Dec 08, 2014 at 11:03:58AM -0800, Bill Spitzak wrote:
Shouldn't this use the same api as the input methods, since it is in fact an
input method?
please explain
Never mind, I think this is not talking about text input, but about
using U
On Mon, Dec 08, 2014 at 06:26:11PM -0800, Bryce Harrington wrote:
> The table of contents is out of order:
>
> ..
> Chapter 4. Wayland Protocol and Model of Operation
> Appendix A. Wayland Protocol Specification
> Chapter 5. Wayland Library
>
> The protocol specification docs and the wa
On Mon, Dec 08, 2014 at 06:43:14PM -0800, Bill Spitzak wrote:
> I made the same change in the patches I submitted, and also split
> the client and server into different Appendicies.
Ah, sorry, didn't see that.
> On 12/08/2014 06:26 PM, Bryce Harrington wrote:
> >The table of contents is out of o
> -Original Message-
> From: wayland-devel
> [mailto:wayland-devel-boun...@lists.freedesktop.org] On Behalf Of
> Pekka Paalanen
> Sent: Monday, December 08, 2014 9:02 PM
> To: wayland-devel@lists.freedesktop.org
> Subject: Where should project Weston go?
>
> Dear Wayland community,
>
>
I made the same change in the patches I submitted, and also split the
client and server into different Appendicies.
On 12/08/2014 06:26 PM, Bryce Harrington wrote:
The table of contents is out of order:
..
Chapter 4. Wayland Protocol and Model of Operation
Appendix A. Wayland Protoco
On Mon, Dec 08, 2014 at 11:03:58AM -0800, Bill Spitzak wrote:
> Shouldn't this use the same api as the input methods, since it is in fact an
> input method?
please explain
> On 12/07/2014 10:05 PM, Peter Hutterer wrote:
> >Some devices don't rely on keycodes + xkb layout but rather send a specif
The table of contents is out of order:
..
Chapter 4. Wayland Protocol and Model of Operation
Appendix A. Wayland Protocol Specification
Chapter 5. Wayland Library
The protocol specification docs and the wayland library docs both are
generated documentation from source code as opposed to
How about adding more info like following to clearly say which shell output
this log?
weston_log("ivi-shell: No ivi-module set in weston.conf\n");
BR,
Nobuhiko Tanibata
> -Original Message-
> From: wayland-devel
> [mailto:wayland-devel-boun...@lists.freedesktop.org] On Behalf Of
> Ond?ej
You are right that the fact that it is along the pen is not obvious from
"Z". However this is actually true of "X" and "Y" (one of them could be
the angle in the plane defined by the other tilt).
Roll probably is good, but it still seems to me that Z is more common,
also it looks like the evde
On Mon, Dec 08, 2014 at 10:46:44AM +0100, Hans de Goede wrote:
> We use 2 mechanisms to unregister the trackpoint event listener depending on
> device removal order.
>
> 1) We have a device_removed callback, if the trackpoint gets removed before
> the touchpad, this gets called, sees the device be
On Mon, Dec 08, 2014 at 10:46:43AM +0100, Hans de Goede wrote:
> Some dispatchers may want to do some cleanup at remove time, rather then at
> destroy time.
>
> Signed-off-by: Hans de Goede
> ---
> src/evdev-mt-touchpad.c | 1 +
> src/evdev.c | 4
> src/evdev.h | 3 +
On Mon, Dec 08, 2014 at 02:01:32PM +0200, Pekka Paalanen wrote:
> Dear Wayland community,
>
> I would like to start a discussion on what Weston really is, and where
> it should go, if only to confirm that our concensus still holds.
Thanks for opening discussion on this. I suspect a lot of us hav
On Mon, Dec 08, 2014 at 12:13:17PM -0800, Bill Spitzak wrote:
> Why not call it Z instead of TWIST?
>
> I'm pretty certain that is a common term for this movement, and that "twist"
> is a rather strange term ("roll" is used more). And Z has the advantage that
> it also implies that counter-clockwi
On 12/08/2014 12:13 PM, Bill Spitzak wrote:
> Why not call it Z instead of TWIST?
>
> I'm pretty certain that is a common term for this movement, and that
> "twist" is a rather strange term ("roll" is used more). And Z has the
> advantage that it also implies that counter-clockwise is positive.
>
Why not call it Z instead of TWIST?
I'm pretty certain that is a common term for this movement, and that
"twist" is a rather strange term ("roll" is used more). And Z has the
advantage that it also implies that counter-clockwise is positive.
On 12/08/2014 09:59 AM, Jason Gerecke wrote:
---
On 12/08/2014 09:59 AM, Jason Gerecke wrote:
+normalize_double_ended(const struct input_absinfo * absinfo) {
+ /* Map from (0, 1) to the (-1, 1) range */
I think you mean "Map from (min, max) to the (-1, 1) range"
___
wayland-devel mailing list
On 12/08/2014 06:07 AM, Jonas Ådahl wrote:
On Tue, Dec 02, 2014 at 02:39:21PM -0800, Bill Spitzak wrote:
- Does this need some id of the triggering event? Mostly to determine if the
surface had the pointer focus at the time the request was made.
It does not, and the lock is postponed until t
However I think the decision was to only require Doxygen 1.6 and
therefore the tildes don't work, and you must use \code. Is this
correct? This is what is currently in git head.
On 12/08/2014 01:35 AM, Pekka Paalanen wrote:
On Fri, 05 Dec 2014 12:53:28 -0800
Bill Spitzak wrote:
On 12/05/201
Shouldn't this use the same api as the input methods, since it is in
fact an input method?
On 12/07/2014 10:05 PM, Peter Hutterer wrote:
Some devices don't rely on keycodes + xkb layout but rather send a specific
keysym (or multiple) in response to physical button presses. This is the case
for
Signed-off-by: Jason Gerecke
Acked-by: Peter Hutterer
---
test/litest-wacom-intuos-tablet.c | 3 +++
test/tablet.c | 41 +--
2 files changed, 42 insertions(+), 2 deletions(-)
diff --git a/test/litest-wacom-intuos-tablet.c
b/test/litest-w
Some Wacom tablets can report the rotation of the pen about its barrel
in the ABS_Z axis. Report this via LIBINPUT_TABLET_AXIS_TWIST.
Signed-off-by: Jason Gerecke
Acked-by: Peter Hutterer
---
src/evdev-tablet.c | 6 ++
src/evdev-tablet.h | 6 ++
src/libinput.c | 1 +
src/libinput.h
Changes the names to reflect the functionality, not the use case. Also
defines one in terms of the other so that we aren't repeating ourselves.
Signed-off-by: Jason Gerecke
Acked-by: Peter Hutterer
---
src/evdev-tablet.c | 15 ++-
1 file changed, 6 insertions(+), 9 deletions(-)
dif
A keyboard might not be present in a seat, so check that before
dereferencing keyboard related pointers.
Also, use the keyboard pointer we set to shorten the code a little bit.
Signed-off-by: Derek Foreman
---
Made the check similar to the dereference.
src/text-backend.c | 16 ++--
Adding simple notes on DocBook dependencies needed when building on Arch Linux.
Without these being present the documentation build will attempt network access
and fail outright or warn and then not produce correct results when no Internet
access is present.
Fixes: https://bugs.freedesktop.org/sho
On Tue, Dec 02, 2014 at 02:39:21PM -0800, Bill Spitzak wrote:
> On 12/02/2014 05:49 AM, Jonas Ådahl wrote:
>
> >+
> >+
> >+The lock_pointer request lets the client disable absolute pointer
> >+movements, locking the pointer to a position.
> >+
> >+There may not be
On Thu, 4 Dec 2014 13:23:57 +0200
Pekka Paalanen wrote:
> On Tue, 02 Dec 2014 12:12:28 -0800
> Bill Spitzak wrote:
>
> > On 12/02/2014 05:45 AM, Pekka Paalanen wrote:
> > > From: Pekka Paalanen
> >
> > > + if (!s->get_label || s->get_label(s, d, sizeof(d)) < 0) {
> > > + d[0] = '\0';
On Mon, Dec 08, 2014 at 10:46:54AM +0100, Hans de Goede wrote:
> From: Carlos Garnacho
>
> Signed-off-by: Carlos Garnacho
pushed, thanks. fwiw, you can push patches like this directly to the repo, I
don't think they'll trigger big discussions on design :)
Cheers,
Peter
> ---
> src/evdev.c
Dear Wayland community,
I would like to start a discussion on what Weston really is, and where
it should go, if only to confirm that our concensus still holds.
I feel the need for it, because I personally find it sometimes hard to
judge whether a big new feature is a good idea or out of scope.
If
What annoyed me was weston silently ignoring the tty argument in certain
conditions (you have to specify a new user argument while being root).
I reasoned that user access to the tty should be set up by the kernel
policies, and we should not enforce the policy at weston level. If the
system is con
From: Carlos Garnacho
Signed-off-by: Carlos Garnacho
---
src/evdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/evdev.c b/src/evdev.c
index 4490562..c8ca384 100644
--- a/src/evdev.c
+++ b/src/evdev.c
@@ -2032,7 +2032,7 @@ evdev_device_remove(struct evdev_device *dev
Hi,
On Wednesday, October 2, 2013, Alex DAMIAN
wrote:
>
> Current behaviour of the tty parameter is to take effect
> only if there is a new user starting up.
>
> Since it is useful to start weston-launch with a command line
> specified tty, I'm changing the semantics of the tty parameter:
>
> * t
Some dispatchers may want to do some cleanup at remove time, rather then at
destroy time.
Signed-off-by: Hans de Goede
---
src/evdev-mt-touchpad.c | 1 +
src/evdev.c | 4
src/evdev.h | 3 +++
3 files changed, 8 insertions(+)
diff --git a/src/evdev-mt-touchpad.c b/sr
We use 2 mechanisms to unregister the trackpoint event listener depending on
device removal order.
1) We have a device_removed callback, if the trackpoint gets removed before
the touchpad, this gets called, sees the device being removed is the trackpoint
and unregisters the listener
2) If the tou
On Fri, 05 Dec 2014 12:53:28 -0800
Bill Spitzak wrote:
> On 12/05/2014 06:44 AM, Pekka Paalanen wrote:
>
> > do you have any suggestions on how to get rid of the asterisks in front
> > of code examples?
>
> All I can say is that this appears to be a Doxygen bug, and it depends
> both on the ve
On Fri, Dec 05, 2014 at 12:53:28PM -0800, Bill Spitzak wrote:
> On 12/05/2014 06:44 AM, Pekka Paalanen wrote:
>
> >do you have any suggestions on how to get rid of the asterisks in front
> >of code examples?
>
> All I can say is that this appears to be a Doxygen bug, and it depends both
> on the
Hi,
On 08-12-14 04:52, Peter Hutterer wrote:
Avoid mismatches in what the caller expects vs what libinput actually
provides when building against newer/older versions of libinput.
Signed-off-by: Peter Hutterer
Looks good:
Reviewed-by: Hans de Goede
Regards,
Hans
---
This patch applies
On Fri, 05 Dec 2014 07:39:04 -0800
"Jon A. Cruz" wrote:
>
>
> On 12/05/2014 07:09 AM, Pekka Paalanen wrote:
> >
> > Hi,
> >
> > looking at doc/doxygen/wayland.doxygen.in it says
> > # Doxyfile 1.7.6.1
> >
> > Do we know this works with Doxygen 1.6 or should we require 1.7?
> >
> > Not that
40 matches
Mail list logo
