Daniel!
As per your logic, I see wl_list APIs exposed etc, which shouldn't be part
of libwayland as well.
similarly, wl_fixed_to_double and wl_array shouldn't be part of the window
system. Isnt it?
I can make inline functions if that helps.
Btw here is an API patch, which has not be reviewed
On Tue, 28 Oct 2014 16:46:24 +
Daniel Stone dan...@fooishbar.org wrote:
Hi,
On 24 October 2014 11:18, Pekka Paalanen pekka.paala...@collabora.co.uk
wrote:
On Fri, 24 Oct 2014 10:28:57 +0100
Daniel Stone dan...@fooishbar.org wrote:
Hmm. Can we please use weston_client_start
2014-10-29 8:45 GMT+02:00 Imran Zaman imran.za...@gmail.com:
Daniel!
As per your logic, I see wl_list APIs exposed etc, which shouldn't be part
of libwayland as well.
similarly, wl_fixed_to_double and wl_array shouldn't be part of the window
system. Isnt it?
I can make inline functions if
On Wed, Oct 29, 2014 at 10:09 AM, Giulio Camuffo giuliocamu...@gmail.com
wrote:
2014-10-29 8:45 GMT+02:00 Imran Zaman imran.za...@gmail.com:
Daniel!
As per your logic, I see wl_list APIs exposed etc, which shouldn't be
part
of libwayland as well.
similarly, wl_fixed_to_double and
Hi,
thanks for review!
On 27 October 2014 18:50, Bill Spitzak spit...@gmail.com wrote:
On 10/15/2014 01:16 AM, Marek Chalupa wrote:
+ shadow_height = height / 2;
+
+ /* when the height is odd, we need some part of
the
+
set_fullscreen has been sending configure before changing the state
and xwayland windows added border to the fullscreen size.
This fixes the bug:
https://bugs.freedesktop.org/show_bug.cgi?id=83502
Signed-off-by: Marek Chalupa mchqwe...@gmail.com
---
desktop-shell/shell.c | 4 ++--
This function is used and clearly designed only for drawing the shadows.
Rename it so that it has name after what it does and also move some
common code into the function.
Signed-off-by: Marek Chalupa mchqwe...@gmail.com
---
shared/cairo-util.c | 12 ++--
shared/cairo-util.h
If the client is small ( 128 pixels in any ward),
then the shadows overlap and create dark lines behind clients.
This is a problem mosly with pop-up menues. The lines become observable
when the menu has less than three items. The other case is when
the client doesn't restrict its size when
Log a message when the kernel event queue overflows and events are dropped.
After 10 messages logging stops to avoid flooding the logs if the condition
is persistent.
---
src/evdev.c | 11 +++
src/evdev.h | 4
2 files changed, 15 insertions(+)
diff --git a/src/evdev.c b/src/evdev.c
Thank you for the detailed gyaan. I will look into the sub-surface
protocol as an alternative. What I do as of now is have the 2 threads on a
3 second timer where threadA renders triangle for 3 seconds then signals a
mutex condition and wakes up threadB which renders gears for 3 seconds and
so on
Currently, once we've reached our main's wl_display_run(), we always
return ret=EXIT_SUCCESS when weston terminates through wl_display_terminate.
This patch makes it possible to specify another return value by setting
prior to terminating Weston. This is useful for automated tests that want
to
Weston will not repaint until previous update has been acked by
a page-flip event coming from the drm driver. However, some buggy drivers
won't return those events or will stop sending them at some point and
Weston output repaints will completely freeze. To ease developers' task in
testing their
Currently, once we've reached our main's wl_display_run(), we always
return ret=EXIT_SUCCESS when weston terminates through wl_display_terminate.
This patch makes it possible to specify another return value by setting
prior to terminating Weston. This is useful for automated tests that want
to
Weston will not repaint until previous update has been acked by
a page-flip event coming from the drm driver. However, some buggy drivers
won't return those events or will stop sending them at some point and
Weston output repaints will completely freeze. To ease developers' task in
testing their
On 10/29/2014 11:13 AM, Frederic Plourde wrote:
This watchdog timer (WDT) implementation is software only and includes
basic features usually found in a WDT. We simply exit Weston gracefully
with an exit code when the dog barks.
The watchdog timeout value can be set via weston.ini by adding
On Mon, Oct 27, 2014 at 11:17:48AM -0400, Frederic Plourde wrote:
Weston's idle timeout can already be set via the '-i' command-line
option, but this patch lets users specify it also via weston.ini.
Note that the command-line option takes precedence over the .ini,
should the option be set by
On Mon, Oct 27, 2014 at 03:13:19PM +, Javier Jardón wrote:
This fixes this build failure:
/usr/lib/gcc/x86_64-unknown-linux-gnu/4.7.3/../../../../x86_64-unknown-linux-gnu/bin/ld:
clients/weston_multi_resource-multi-resource.o: undefined reference to
symbol 'clock_gettime@@GLIBC_2.2.5'
On Tuesday 28 October 2014, 15:45:18, Kai-Uwe Behrmann wrote:
Am 27.10.2014 um 19:07 schrieb Niels Ole Salscheider:
The support to mask the area of a surface so that its color space is not
converted has been removed. Instead, the color profile of the main output
of that surface can be
On 14-10-29 02:45 PM, Bill Spitzak wrote:
On 10/29/2014 11:13 AM, Frederic Plourde wrote:
This watchdog timer (WDT) implementation is software only and includes
basic features usually found in a WDT. We simply exit Weston gracefully
with an exit code when the dog barks.
The watchdog timeout
On Mon, Oct 27, 2014 at 09:14:40AM +0100, Marek Chalupa wrote:
The callback returns always with the same serial,
which is not right (it's serial, not constant...).
This test highlights the bug.
Signed-off-by: Marek Chalupa mchqwe...@gmail.com
---
tests/display-test.c | 55
On 14-10-29 02:57 PM, Bryce Harrington wrote:
On Mon, Oct 27, 2014 at 11:17:48AM -0400, Frederic Plourde wrote:
Weston's idle timeout can already be set via the '-i' command-line
option, but this patch lets users specify it also via weston.ini.
Note that the command-line option takes precedence
Hi,
On Wednesday, October 29, 2014, Pekka Paalanen
pekka.paala...@collabora.co.uk wrote:
On Tue, 28 Oct 2014 16:46:24 +
Daniel Stone dan...@fooishbar.org javascript:; wrote:
On 24 October 2014 11:18, Pekka Paalanen pekka.paala...@collabora.co.uk
javascript:;
wrote:
I think we all
On 10/29/2014 12:19 PM, Frederic Plourde wrote:
Mhh... you mean something like :
static int
drm_output_watchdog_timer_create(struct drm_output *output)
{
struct wl_event_loop *loop = NULL;
struct weston_compositor *ec = output_base-compositor;
loop =
Based on Jon A. Cruz patch. I tested the build on my 12.04 and Linux Mint
machines and it appears to be correct, though there are certainly no
guarantees as the machines were not cleaned of all installed packages.
___
wayland-devel mailing list
Changes are:
- enable documentaion
- libinput backend is enabled by default now
- Updated the date
---
mint17.html |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/mint17.html b/mint17.html
index 173e2f4..ae1c5a8 100644
--- a/mint17.html
+++ b/mint17.html
@@ -12,7
This was tested on the same machine as before. Changes are:
- xmlto is required (it was already installed on my machine so I missed this)
- libinput is enabled by default
- fixed date
Several x11 proto packages that seem to be required on my Mint 14.04 machine
are not necessary here:
On Wed, Oct 29, 2014 at 04:10:22PM -0700, Bill Spitzak wrote:
Based on Jon A. Cruz patch. I tested the build on my 12.04 and Linux Mint
machines and it appears to be correct, though there are certainly no
guarantees as the machines were not cleaned of all installed packages.
LGTM,
Reviewed-by:
I've seen many Wayland specific error but no patch solved for me.
I've also tried different tags but it's always the same:
unknown type name 'VADriverContextP'
in file included from i965_drv_video.c
which is i965_output_wayland.h
After that it fails but I was used to be able to build everything
28 matches
Mail list logo
