From: Quentin Glidic
We can then add tests which do not use Weston in the test suite.
Signed-off-by: Quentin Glidic
---
Further patches are coming to move tests around and add one
(for option parsing changes)
tests/.gitignore | 7 +--
tests/Makefile.am | 41 ++-
On Tue, Jun 11, 2013 at 06:21:32PM +0300, Ander Conselvan de Oliveira wrote:
> Document what we expect in terms of commit messages and coding style.
> New contributors are usually unaware of this, so it is good to have a
> document to point them too.
> ---
>
> I probably haven't captured everythin
On Mon, 2013-06-17 at 18:08 +0200, Marc Chalain wrote:
> Hello,
> My first observation is we need a PC keyboard support at the end
> ( often a virtual keyboard).
There's an input method procotol that we intended to use for virtual
keyboards. Try weston's clients/editor.c together with the exampl
The current specified behavior does not allow a null surface in either of
these events. However, if the client calls wl_surface.destroy while the
surface has focus then the leave handler will get a null surface anyway
because the proxy corresponding to the wl_surface no longer exists. This
change
Hi,
On 14 June 2013 17:42, Rob Bradford wrote:
> In embedded environments, devices that appear as evdev "keyboards" often
> have no resemblence to PC-style keyboards. It is not uncommon for such
> environments to have no concept of modifier keys and no need for XKB key
> mapping; in these cases
On segunda-feira, 17 de junho de 2013 12.14.39, Abhijit Potnis wrote:
> :). I know Qt5.0 is already old ! It's my employers client who has this
> requirement for Qt 4.8 !
That's exactly the problem.
Are you modifying an existing application? It's probably an application using
Qt for X11 or Qt fo
On Sun, Jun 16, 2013 at 01:29:36PM +0300, Pekka Paalanen wrote:
> On Fri, 14 Jun 2013 17:42:08 +0100
> Rob Bradford wrote:
>
> > From: Matt Roper
> >
> > In embedded environments, devices that appear as evdev "keyboards" often
> > have no resemblence to PC-style keyboards. It is not uncommon f
Hi Marc,
On 17 June 2013 17:08, Marc Chalain wrote:
> I already wrote an email on this mailing list about the use of xkbcommon for
> embedded solution.
> I had the same problem as Robert, and I disabled the check of the keymap.
> The problem is that we have number of keyboards as input device, on
Hello,
I already wrote an email on this mailing list about the use of xkbcommon
for embedded solution.
I had the same problem as Robert, and I disabled the check of the keymap.
The problem is that we have number of keyboards as input device, on the
same platform, and it's not possible to define a
Hey guys,
I'm Rafael Fonseca, a brazilian Master's degree in Computer Science
student, and I was accepted in this year Google Summer of Code to work
in Gnome and Wayland.
I'll be working on porting the color management done in Gnome (and X)
to Wayland. I'm still on the studying and understanding
Hi All,
After looking into it a bit more, it appears as if the proper thing to do
is to allow a null surface in wl_pointer.leave, wl_keyboard.leave, etc.
Right now, that's what the clients are seeing anyway because
wl_surface_destroy destroys the associated proxy so there is no valid way
to call a
11 matches
Mail list logo
