On Mon, 3 Jun 2013 16:21:48 +0200
John Kåre Alsaker wrote:
> On Mon, Jun 3, 2013 at 2:22 PM, Pekka Paalanen wrote:
>
> > On Tue, 28 May 2013 19:27:35 +0200
> > John Kåre Alsaker wrote:
> >
> > > + Conceptually simple to implement. Compositors doesn't have to deal with
> > > scaling for subsurf
On Mon, Jun 3, 2013 at 10:21 PM, Bill Spitzak wrote:
> + Clients get input in exact pixels (no rounding errors).
>> + Clients doesn't have to transform input events in order to match the
>> sizes used by buffers.
>
> You said "pels" don't match buffer pixels. Therefore a transformation is
> nee
On Tue, May 28, 2013 at 05:28:49PM -0700, Sinclair Yeh wrote:
> v3:
> * Removed unnecessary parentheses
> * Added check for switching from EGL image to SHM buffer
> * Moved shader assignment out of IF condition
>
> v2:
> Fixed the wrong comparison
>
> v1:
> Depending on specific DRI driver implem
From: "U. Artie Eoff"
The available emulators are "uinput" and "notify". To choose
which emulator to use, define the environment variable:
WESTON_WFITS_INPUT_EMULATOR
equal to the name of the desired emulator before loading the
weston-wfits.so module into Weston.
For example:
$ export WESTO
On Mon, Jun 03, 2013 at 12:24:09PM -0300, Eduardo Lima (Etrunko) wrote:
> From: "Eduardo Lima (Etrunko)"
>
> These can be used by external clients to check the installation path
Makes sense, patch applied.
Kristian
> Signed-off-by: Eduardo Lima (Etrunko)
> ---
> src/weston.pc.in | 2 ++
> 1
On Mon, Jun 03, 2013 at 06:46:13PM +0100, Rob Bradford wrote:
> From: Rob Bradford
>
> Rather than failing if we cannot open any single device fail the input
> setup if there are no input devices added.
>
> https://bugs.freedesktop.org/show_bug.cgi?id=64506
Thanks Rob, patch applied.
Kristian
On Thu, May 30, 2013 at 01:57:00PM +0200, Jan Arne Petersen wrote:
> From: Jan Arne Petersen
>
> Fix some bugs I noticed when testing the editor example with
> latest Wayland enabled Maliit.
Thanks Jan, all committed.
Kristian
> Jan Arne Petersen (5):
> editor: Fix text selection
> editor:
On Thu, May 30, 2013 at 03:16:40PM +0200, Armin K wrote:
> This patch adds auto detection for presence of
> the colord and libunwind packages.
> ---
> configure.ac | 43 +++
> 1 file changed, 31 insertions(+), 12 deletions(-)
That is better, thanks Armin.
On Mon, Jun 03, 2013 at 10:55:47PM +0200, Hardening wrote:
> The RDP compositor was ignoring mouse wheel events, this patch adds
> support for it.
Committed, thanks.
Kristian
> ---
> src/compositor-rdp.c | 19 ++-
> 1 file changed, 18 insertions(+), 1 deletion(-)
>
> diff --git
On Mon, Jun 03, 2013 at 04:22:31PM -0700, U. Artie Eoff wrote:
> From: "U. Artie Eoff"
>
> exit() calls atexit() handlers and C++ destructors (e.g. a C++
> weston module) which could destroy state that the main process
> depends on (e.g. ioctl's, tmpfiles, sockets, etc...). If an exec
> fails, c
Jason Ekstrand wrote:
I think I'm begining to see what you and John have been suggesting.
While I think Alexander's proposal will work well enough for the
standard case, I think this also has merit. If I were to sum up, I'd
say I was "cautiously supportive" of the above. It does seem to sol
Can we make sure this gets backported to 1.1, too?
> -Original Message-
> From: Eoff, Ullysses A
> Sent: Monday, June 03, 2013 4:23 PM
> To: wayland-devel@lists.freedesktop.org
> Cc: Eoff, Ullysses A
> Subject: [PATCH weston v2] use _exit instead of exit if client fails to exec
>
> From:
From: "U. Artie Eoff"
exit() calls atexit() handlers and C++ destructors (e.g. a C++
weston module) which could destroy state that the main process
depends on (e.g. ioctl's, tmpfiles, sockets, etc...). If an exec
fails, call _exit() instead of exit().
v2: prefer _exit over _Exit
Signed-off-by:
From: "U. Artie Eoff"
exit() calls atexit() handlers and C++ destructors (e.g. a C++
weston module) which could destroy state that the main process
depends on (e.g. ioctl's, tmpfiles, sockets, etc...). If an exec
fails, call _Exit() instead of exit().
Signed-off-by: U. Artie Eoff
---
src/comp
On Mon, Jun 3, 2013 at 3:21 PM, Bill Spitzak wrote:
> It appears John Alsaker is proposing exactly the same change I have been
> proposing. I think we are having a hard time explaining it however.
>
>
> Pekka Paalanen wrote:
>
>> On Tue, 28 May 2013 19:27:35 +0200
>> John Kåre Alsaker wrote:
>>
The RDP compositor was ignoring mouse wheel events, this patch adds
support for it.
---
src/compositor-rdp.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/src/compositor-rdp.c b/src/compositor-rdp.c
index e855ba6..b81d789 100644
--- a/src/compositor-rdp.c
Le 03/06/2013 22:41, Bill Spitzak a écrit :
Hardening wrote:
+#define DEFAULT_AXIS_STEP_DISTANCE wl_fixed_from_int(10)
+axis = DEFAULT_AXIS_STEP_DISTANCE * ((flags & 0xff) / 120);
This can only make the fixed numbers 0, 10.0, and 20.0. Is this correct?
A wild guess is that this is
Hardening wrote:
+#define DEFAULT_AXIS_STEP_DISTANCE wl_fixed_from_int(10)
+ axis = DEFAULT_AXIS_STEP_DISTANCE * ((flags & 0xff) / 120);
This can only make the fixed numbers 0, 10.0, and 20.0. Is this correct?
A wild guess is that this is actually what is wanted:
axis =
It appears John Alsaker is proposing exactly the same change I have been
proposing. I think we are having a hard time explaining it however.
Pekka Paalanen wrote:
On Tue, 28 May 2013 19:27:35 +0200
John Kåre Alsaker wrote:
My proposal is simply to let the compositor tell the client how much
The RDP compositor was ignoring mouse wheel events, this patch adds
support for it.
---
src/compositor-rdp.c | 19 ++-
1 file changed, 18 insertions(+), 1 deletion(-)
diff --git a/src/compositor-rdp.c b/src/compositor-rdp.c
index e855ba6..e234816 100644
--- a/src/compositor-rdp.c
Hi Daniel,
On Mon, Jun 3, 2013 at 11:45 AM, Daniel Stone wrote:
>
> The usual pattern here is to set the default to 'auto', which will
> check whether or not the dependency is installed and select yes or no
> accordingly. If someone explicitly passes --enable-colord and it's
> not installed, we
http://lists.freedesktop.org/archives/wayland-devel/2013-May/009554.html
Next time check list before taking time to duplicate the effort.
- Original Message -
From: Othman, Ossama
Sent: 06/03/13 08:44 PM
To: sardemff7+wayl...@sardemff7.net
Subject: Re: Compiling weston now needs colord
Hi,
On 3 June 2013 19:41, Ossama Othman wrote:
> -AM_CONDITIONAL(ENABLE_COLORD,
> - test "x$enable_colord" = "xyes")
> if test x$enable_colord = xyes; then
> - PKG_CHECK_MODULES(COLORD, colord >= 0.1.27)
> + PKG_CHECK_MODULES([COLORD],
> +[colord >= 0.1.27],
>
Hi,
On Thu, May 30, 2013 at 12:42 AM, wrote:
> On 30/05/2013 08:24, Michael Hasselmann wrote:
>
>> On Tue, 2013-05-28 at 22:16 -0700, Bill Spitzak wrote:
>>
>>> Running autogen.sh in weston with --disable-colord works to avoid this,
>>> I suspect nothing I care about is lost this way.
>>>
>>
>>
Both colord and libunwind are optional dependencies. As such, the
configure script should not exit with a failure if they are missing.
Issue warnings instead if either colord or libunwind is missing and
wasn't found.
This also allows "make distcheck" to succeed on platforms that don't
have colord
From: Rob Bradford
Rather than failing if we cannot open any single device fail the input
setup if there are no input devices added.
https://bugs.freedesktop.org/show_bug.cgi?id=64506
---
src/udev-seat.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/src/udev-seat.c b/
From: "Eduardo Lima (Etrunko)"
These can be used by external clients to check the installation path
Signed-off-by: Eduardo Lima (Etrunko)
---
src/weston.pc.in | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/weston.pc.in b/src/weston.pc.in
index 537cc89..828cb1f 100644
--- a/src/westo
On Mon, Jun 3, 2013 at 4:36 AM, Ander Conselvan de Oliveira <
conselv...@gmail.com> wrote:
> On 06/02/2013 01:40 AM, Jason Ekstrand wrote:
>
>> The implementation in this commit allows for one bit worth of flags. If
>> more flags are desired at a future date, then the wl_map implementation
>> wil
On Mon, Jun 3, 2013 at 2:22 PM, Pekka Paalanen wrote:
> On Tue, 28 May 2013 19:27:35 +0200
> John Kåre Alsaker wrote:
>
> > My proposal is simply to let the compositor tell the client how much
> larger
> > it wants the client to render content. The client can then tell the
> > compositor how muc
On 03/06/13 15:50, ppaala...@gmail.com wrote:
> From: Pekka Paalanen
>
> Signed-off-by: Pekka Paalanen
> Cc: Daniel Stone
> Cc: Alex Bradbury
>
> ---
>
> Darxus, could you wait till tomorrow until pushing this, so Daniel and
> Alex can comment, if there's anything to add?
>
> Thanks,
> pq
>
Hi,
Looks good to me (pending getting our key in the keyring), but you
probably want to mention that this only works when running as 'pi'.
Cheers,
Daniel
On 3 June 2013 14:50, wrote:
> From: Pekka Paalanen
>
> Signed-off-by: Pekka Paalanen
> Cc: Daniel Stone
> Cc: Alex Bradbury
>
> ---
>
>
From: Pekka Paalanen
Signed-off-by: Pekka Paalanen
Cc: Daniel Stone
Cc: Alex Bradbury
---
Darxus, could you wait till tomorrow until pushing this, so Daniel and
Alex can comment, if there's anything to add?
Thanks,
pq
---
raspberrypi.html | 25 +
1 file changed, 25
On Mon, 3 Jun 2013 13:24:23 +0100
Alex Bradbury wrote:
> On 3 June 2013 12:58, wrote:
> > From: Pekka Paalanen
> > It's not strictly necessary to use rpi-update, but I don't know how old
> > firmware and libs are in the Raspbian packages, so recommend it still.
>
> They currently contain firm
On 3 June 2013 12:58, wrote:
> From: Pekka Paalanen
> It's not strictly necessary to use rpi-update, but I don't know how old
> firmware and libs are in the Raspbian packages, so recommend it still.
They currently contain firmware as of 2013-05-24.
I don't know if it's worth noting in this doc
On Tue, 28 May 2013 19:27:35 +0200
John Kåre Alsaker wrote:
> My proposal is simply to let the compositor tell the client how much larger
> it wants the client to render content. The client can then tell the
> compositor how much larger it made content in the window. Armed with this
> information
From: Rob Bradford
This provides the ability for a client to differentiate events from
different seats in a multiple seat environment.
v2: handled versioning correctly based on feedback from Daniel and Ander
---
protocol/wayland.xml | 14 +-
1 file changed, 13 insertions(+), 1 delet
Thanks, committed. (HTML validates.)
On 06/03, ppaala...@gmail.com wrote:
> From: Pekka Paalanen
>
> Either libraspberrypi-dev package or running rpi-update is needed to get
> the display API libraries.
>
> It's not strictly necessary to use rpi-update, but I don't know how old
> firmware and
From: Pekka Paalanen
Either libraspberrypi-dev package or running rpi-update is needed to get
the display API libraries.
It's not strictly necessary to use rpi-update, but I don't know how old
firmware and libs are in the Raspbian packages, so recommend it still.
---
raspberrypi.html | 11 +
On 06/02/2013 01:40 AM, Jason Ekstrand wrote:
The implementation in this commit allows for one bit worth of flags. If
more flags are desired at a future date, then the wl_map implementation
will have to change but the wl_map API will not.
I couldn't find a description of what WL_MAP_ENTRY_LEGA
On 30/05/2013 08:24, Michael Hasselmann wrote:
On Tue, 2013-05-28 at 22:16 -0700, Bill Spitzak wrote:
Running autogen.sh in weston with --disable-colord works to avoid this,
I suspect nothing I care about is lost this way.
I ran into the very same problems. I would have preferred if such new
d
On 05/31/2013 08:40 PM, Daniel Stone wrote:
Hi,
On 31 May 2013 13:08, Rob Bradford wrote:
+
This needs since="2".
And the new event needs to appear after all version 1 events and
requests. The scanner expects the since field to be non-decreasing. It
will throw an error if it finds a
41 matches
Mail list logo
