On Thu, Aug 22, 2013 at 04:23:48PM +0200, Giovanni Campagna wrote:
> From: Giovanni Campagna
>
> Drop xf86InitialConfiguration, which just gets in the way
> of the compositor doing its own output arrangement, and transform
> wayland events into the appropriate low-level xf86 calls to
> keep the s
On Thu, Aug 22, 2013 at 09:46:28AM +0100, Stefan Schmidt wrote:
> Treating some specific sensors as input devices. In particular
> adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
>
> Using these sensor as input for apps and games. Not covering any
> background apps or servic
Signed-off-by: Jason Ekstrand
---
src/compositor.c | 12 ++--
weston.ini | 3 ++-
2 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index e9ba0fd..bb66fc7 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -3224,6 +3224,7 @@ us
Sorry, I had a vim blooper in this one. New patch coming.
--Jason Ekstrand
On Thu, Aug 22, 2013 at 5:24 PM, Jason Ekstrand wrote:
> Signed-off-by: Jason Ekstrand
> ---
> src/compositor.c | 14 +++---
> weston.ini | 3 ++-
> 2 files changed, 13 insertions(+), 4 deletions(-)
>
>
Signed-off-by: Jason Ekstrand
---
src/compositor.c | 14 +++---
weston.ini | 3 ++-
2 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index e9ba0fd..7454050 100644
--- a/src/compositor.c
+++ b/src/compositor.c
@@ -3224,7 +3224,8 @@
Hi,
I was told of this thread, perhaps I can make a few comments (sorry if it
doesn't really follow the thread)
[no knowing much about wayland protocol/api]
first thoughts:
* why no timestamp info?
* why no rate info? (not all apps need/want the same speed)
* a magnetometer is not a compass, nor
Jason Ekstrand wrote:
One thing I'm still missing is a way to handle more than one sensor
per type for the future. Input devices like the wii-remote with
nunchuk comes to mind. Having two separate accelerometers which
still would be a the same seat but could not be aggregated.
Daniel Stone wrote:
Actually, rather than use a different set of configs, I'd rather have
a MatchBackend key which would ignore the section, or file, if
specified. So you could have the same files, but with a MatchBackend
"wayland" key to specify the bits you wanted to apply to XWayland.
How's
Hello list,
Without further ado, here are the 1.21 releases of Wayland and Weston.
Tarballs on wayland.freedesktop.org as usual and here's you daily dose
of big hex numbers:
2214b690cb5a4f9695d287f27730c4368e6ef829 wayland-1.2.1.tar.xz
0df6d81aeecc0d5a52ee8ec228f743836aa24448 wayland 1.2.1
Stefan,
Thanks for working on this!
As one general comment (protocol comments below), we need to make sure that
"normal" values are somewhere around 1 to 1000. The wl_fixed type provides
24 bits of integer and 8 bits of fractional precision. The units used
below seemed reasonable to me. That sa
From: Giovanni Campagna
Drop xf86InitialConfiguration, which just gets in the way
of the compositor doing its own output arrangement, and transform
wayland events into the appropriate low-level xf86 calls to
keep the screen size updated.
Kristian: after the rebase it was crashing for me too, had
Hello.
On 08/22/2013 09:46 AM, Stefan Schmidt wrote:
Treating some specific sensors as input devices. In particular
adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
Using these sensor as input for apps and games. Not covering any
background apps or services with this proto
Treating some specific sensors as input devices. In particular
adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
Using these sensor as input for apps and games. Not covering any
background apps or services with this protocol.
We have requests to start and stop sensor event re
13 matches
Mail list logo
