On Thu, 27 Mar 2014 04:08:15 +
Wang, Quanxian quanxian.w...@intel.com wrote:
Hi, Pq
The information to identify the unique mode: width, height and refresh are
enough? Not enough in theory. But is enough in real world. I have checked
with xrandr. Read the following comment.
Welcome
Hi Jason,
A few comments I have from trying out your fullscreen-shell changes:
On Tue, 18 Mar 2014, Jason Ekstrand wrote:
+static struct ss_seat *
+ss_seat_create(struct shared_output *so, uint32_t id)
+{
+ struct ss_seat *seat;
+
+ seat = zalloc(sizeof *seat);
+ if (seat == NULL)
I don't think the user really knows what refresh is either.
I'm actually curious: is there a reason to ever expose different modes to
the user that have the same width/height but different timings? What's the
rationale for choosing one instead of the other? I know nothing about
display panels,
On Thu, 27 Mar 2014 08:31:34 -0400
Jasper St. Pierre jstpie...@mecheye.net wrote:
I don't think the user really knows what refresh is either.
I'm actually curious: is there a reason to ever expose different modes to
the user that have the same width/height but different timings? What's the
I mean, I'm mostly talking about user configuration in the case of a
desktop, when the user wants to change the mode of the display.
Obviously, it would be best if we could detect hardware edge cases like
that where it's going on the fritz and showing a green tint automatically,
and simply not
On Thu, Mar 27, 2014 at 08:48:02AM +1000, Peter Hutterer wrote:
Both functions accept a series of event types/codes tuples, terminated by -1.
For the even type INPUT_PROP_MAX (an invalid type otherwise) the code is used
as a property to enable.
The _abs function als takes an array of
We've accumulated some changes and bug fixes, so here's a new release.
libxkbcommon 0.4.1
==
- Converted README to markdown and added a Quick Guide to the
documentation, which breezes through the most common parts of
xkbcommon.
Link:
Hi
On Thu, Mar 27, 2014 at 8:22 PM, Ran Benita ran...@gmail.com wrote:
- Added two new functions, xkb_state_key_get_utf{8,32}(). They
combine the operations of xkb_state_key_get_syms() and
xkb_keysym_to_utf{8,32}(), and provide a nicer interface for it
(espcially for
On Thu, Mar 27, 2014 at 09:04:07PM +0100, David Herrmann wrote:
Hi
Hi David
On Thu, Mar 27, 2014 at 8:22 PM, Ran Benita ran...@gmail.com wrote:
- Added two new functions, xkb_state_key_get_utf{8,32}(). They
combine the operations of xkb_state_key_get_syms() and
On Thu, Mar 27, 2014 at 07:34:37PM +0600, Alexander E. Patrakov wrote:
2014-03-27 19:22 GMT+06:00 Alexander E. Patrakov patra...@gmail.com:
(regarding slow scrolling)
I don't think so. I have tried to reproduce the bug by hand. It still
exists, but ./tools/event-debug still picks the
Andrew,
Thanks for reviewing. Comments follow.
On Mar 27, 2014 7:02 AM, Andrew Wedgbury andrew.wedgb...@realvnc.com
wrote:
Hi Jason,
A few comments I have from trying out your fullscreen-shell changes:
On Tue, 18 Mar 2014, Jason Ekstrand wrote:
+static struct ss_seat *
-Original Message-
From: Pekka Paalanen [mailto:ppaala...@gmail.com]
Sent: Thursday, March 27, 2014 9:06 PM
To: Jasper St. Pierre
Cc: Wang, Quanxian; wayland-devel@lists.freedesktop.org
Subject: Re: weston: weston randr protocol for testing and configuration
On Thu, 27 Mar 2014 08:31:34
Remove compiler warning about signed/unsigned comparison. And while we're at
it, rename i to _i in the macro to avoid name clashes.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/libinput-util.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
We depend on device creation on the host system, having the tests run in
parallel runs a risk of random failure.
Ideally we'd just disable for the actual run target, but I couldn't figure out
how to do that.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
test/Makefile.am | 2 ++
1
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
I didn't end up needing this but it seems a nice to have. However, it does
lead to a discussion on how much of the device should we expose to the
caller through libinput.
Right now libinput hides virtually everthing but the sysname and
And redirect the log to stdout. libinput logs to stderr by default, but if
we're running with --verbose we want all msgs on the same stream.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
tools/event-debug.c | 20 +++-
1 file changed, 19 insertions(+), 1 deletion(-)
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
src/evdev-touchpad.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/evdev-touchpad.c b/src/evdev-touchpad.c
index 65c5ea0..1a48441 100644
--- a/src/evdev-touchpad.c
+++ b/src/evdev-touchpad.c
@@ -454,7 +454,7 @@
Looks a bit excessive given how simple the base is but hey, we don't want to
ever break that bit. That'd be embarrassing.
And while we're at it make sure that the 'wrong' event getters return NULL for
each event.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
This requires the uinput
On Thu, Mar 27, 2014 at 10:19:50PM +0600, Alexander E. Patrakov wrote:
Hello.
This is a report of a touchpad firmware bug that I want you to work
around in libinput. I found this bug while testing
xf86-input-libinput. I guess that the synaptics driver already has a
workaround, or the bug
19 matches
Mail list logo
