[PATCH weston] weston-info: fix log message typo

2014-04-18 Thread U. Artie Eoff
Signed-off-by: U. Artie Eoff --- clients/weston-info.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clients/weston-info.c b/clients/weston-info.c index 147dc48..df869e3 100644 --- a/clients/weston-info.c +++ b/clients/weston-info.c @@ -225,7 +225,7 @@ print_output_info(void

Re: [PATCH] Add --no-input option to rpi backend

2014-04-18 Thread Jason Ekstrand
On Fri, Apr 18, 2014 at 9:12 AM, Fernando Herrera wrote: > Adds a --no-input option to the rpi backend so weston can be started > without any input device attached. This is useful for display boxes > without any keyboard/mouse attached > Ok, maybe this is a silly question, but why are we requirin

[PATCH] Add --no-input option to rpi backend

2014-04-18 Thread Fernando Herrera
Adds a --no-input option to the rpi backend so weston can be started without any input device attached. This is useful for display boxes without any keyboard/mouse attached Signed-off-by: Fernando Herrera --- src/compositor-rpi.c | 29 ++--- src/compositor.c |1

Re: [PATCH] editor: react on Enter, Tab, and Up-Down arrow keys

2014-04-18 Thread Manuel Bachmann
This fixes : https://bugs.freedesktop.org/show_bug.cgi?id=77496 Regards, Manuel 2014-04-18 12:50 GMT+02:00 Manuel Bachmann < manuel.bachm...@open.eurogiciel.org>: > The editor will now insert new lines and tabulations when > pressing the corresponding keys on the virtual keyboard. > > The Up an

[PATCH] editor: react on Enter, Tab, and Up-Down arrow keys

2014-04-18 Thread Manuel Bachmann
The editor will now insert new lines and tabulations when pressing the corresponding keys on the virtual keyboard. The Up and Down arrows can be used to navigate through lines. Signed-off-by: Manuel Bachmann --- clients/editor.c | 97 -- 1 f

Re: [RCF wayland] client: extend error handling

2014-04-18 Thread Marek Chalupa
On 15 April 2014 15:36, Pekka Paalanen wrote: > On Fri, 11 Apr 2014 11:39:13 +0200 > Marek Chalupa wrote: > > > When an error occures, than wl_display_get_error() do not > > provide any way of getting know if it was a local error or if it was > > an error event, respectively what object caused t