sorry took so long. forgot to hit send...
On 24/08/2013, at 1:04 AM, Stefan Schmidt wrote:
> Hello.
>
> On 08/22/2013 10:43 PM, Lorn Potter wrote:
>> 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
Hello.
On 08/22/2013 10:43 PM, Lorn Potter wrote:
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?
Arg, that is sitting uncommitted here and th
Hello.
On 08/22/2013 09:20 PM, Bill Spitzak wrote:
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 w
Hello.
On 08/22/2013 04:07 PM, Jason Ekstrand wrote:
Stefan,
Thanks for working on this!
You can thank me once I get this into a state where it gets accepted. ;)
As one general comment (protocol comments below), we need to make sure
that "normal" values are somewhere around 1 to 1000. The w
Hello.
On 08/22/2013 11:45 PM, Bryce W. Harrington wrote:
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 a
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
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.
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
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
these?
regards
Stefan Schmidt
>From 77b19aeff0b1c65625a4aa3b41821c61afa9ea6e Mon Sep 17 00:00:00 2001
From: Stefan Schmidt
Date: Tue, 9 Jul 2013 15:36:41 +0100
Subject: [PATCH] protocol: Extend wayland seat with interfaces for sensor
inputs.
Treating some specific sensors as input devices. In
Hello.
Sorry for the late reply. Got sick in between.
First of all thanks for taking the time to review this and provide feedback.
On 08/12/2013 04:54 PM, David Herrmann wrote:
On Thu, Aug 1, 2013 at 10:39 AM, Stefan Schmidt
wrote:
Treating some specific sensors as input devices. In particula
On Thu, Aug 1, 2013 at 3:39 AM, Stefan Schmidt wrote:
> +
> +
> + Updated sensor data available from compass
> +
> +
> +
> +
> +
These events don't have any units, and there isn't any particular
information about the sensor passed either. Is this suppo
Hi
On Thu, Aug 1, 2013 at 10:39 AM, Stefan Schmidt wrote:
> Treating some specific sensors as input devices. In particular
> adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
>
> We have requests to start and stop sensor event receiving as well as
> events to receive the diff
Hello.
On 08/01/2013 09:39 AM, Stefan Schmidt wrote:
Treating some specific sensors as input devices. In particular
adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
We have requests to start and stop sensor event receiving as well as
events to receive the different axis va
Treating some specific sensors as input devices. In particular
adding support for wl_compass, wl_gyroscope and wl_accelerometer here.
We have requests to start and stop sensor event receiving as well as
events to receive the different axis values for these sensors.
Signed-off-by: Stefan Schmidt
On Tue, 5 Jun 2012 07:23:38 -0700 (PDT)
Claudiu Lupu wrote:
> Hello,
>
> I have a question regarding the compositor and keyboard/mouse inputs and
> surfaces. I have set some surfaces that I am manipulating using the
> ivi-shell. I have another surface that is a virtual keyboar
There's no need to send your message twice. Once is enough.
Thanks,
Scott
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
Hello,
I have a question regarding the compositor and keyboard/mouse inputs and
surfaces. I have set some surfaces that I am manipulating using the ivi-shell.
I have another surface that is a virtual keyboard. When I press a button on the
surface a virtual keyboard driver is sending keyboard
Hello,
I have a question regarding the compositor and keyboard/mouse inputs and
surfaces. I have set some surfaces that I am manipulating using the ivi-shell.
I have another surface that is a virtual keyboard. When I press a button on the
surface a virtual keyboard driver is sending keyboard
21 matches
Mail list logo
