Re: how to run subsurface-test?

On Mon, 24 Jun 2013 07:10:53 + Wang, Quanxian quanxian.w...@intel.com wrote: Hi, Pq Would you like to tell me how to run subsurface-test? I have found the source code in weston/tests is not built out. After checking with configure in Weston, there is no switch to enable how to build

Re: how to run subsurface-test?

On Mon, 24 Jun 2013 09:43:54 + Wang, Quanxian quanxian.w...@intel.com wrote: -Original Message- From: wayland-devel-bounces+quanxian.wang=intel@lists.freedesktop.org [mailto:wayland-devel-bounces+quanxian.wang=intel@lists.freedesktop.org] On Behalf Of Pekka Paalanen

[PATCH]: src/.gitignore: add spring-tool to .gitignore

From 48b5302d7415e35c7f38b89132d3624817450335 Mon Sep 17 00:00:00 2001 From: Nathan Reboud Date: Mon, 24 Jun 2013 16:12:55 +0200 Subject: src/.gitignore: add spring-tool to .gitignore --- src/.gitignore | 1 + 1 file changed, 1 insertion(+) diff --git a/src/.gitignore b/src/.gitignore index

Re: [PATCH weston v2 3/3] build: Make libxkbcommon build-time optional in the compositor

On Sat, Jun 22, 2013 at 12:57:06AM +0100, Daniel Stone wrote: And lastly, you need to bump the dependency on wayland to a version which introduces the WL_KEYBOARD_KEYMAP_FORMAT_NO_KEYMAP enum. I don't think we've done this prior to release before. The expectation being if you run tip of weston

[PATCH wayland v2] protocol: add no_keymap format to keymap formats

From: Rob Bradford r...@linux.intel.com This format is used to specify that the key button events received are not in relation to any key map and that the codes should be interpreted directly. v2: Use zero for the no keymap enum value and enhance the documentation for the enum entry. ---

[PATCH weston v3 1/3] toytoolkit: Allow operation without a keymap

From: Matt Roper matthew.d.ro...@intel.com In preparation for upcoming changes, we want to make sure that apps written with the toy toolkit continue to operate properly if no XKB keymap is received. If there's no XKB keymap, then we shouldn't try to figure out keyboard modifier states (since we

[PATCH weston v3 2/3] input: Add support for making libxkbcommon optional

From: Matt Roper matthew.d.ro...@intel.com 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 libxkbcommon

[PATCH weston v3 3/3] build: Make libxkbcommon build-time optional in the compositor

From: Rob Bradford r...@linux.intel.com v2: Incorporate review feedback from Daniel Stone - improved configure message about the purpose of this option and reorganisation of #ifdefs. --- configure.ac | 15 ++- src/compositor.c | 2 +- src/input.c | 39

Two XML files in weston are not distributed in tarballs

Hello, I have noted that the files subsurface.xml and text-cursor-position.xml are not included in EXTRA_DIST in protocol/Makefile.am, and it seems to me that they should be included in weston tarballs. Cheers, Sven pgpEA4F15Mwgg.pgp Description: PGP signature

[PATCH] Suggesting the surface state functions for maximized and fullscreen.

From: Rafael Antognolli rafael.antogno...@intel.com Just as discussed a lot already on the list, I'm sending a proposal for implementing the surface states, changing from surface types, for fullscreen and maximized. I know that it was said already that fullscreen could be kept as a surface type,

[PATCH] protocol: add state set functions for maximized and fullscreen.

From: Rafael Antognolli rafael.antogno...@intel.com These functions only differ from the previous one because they request that the given state is set, without changing the surface type, thus removing any previously state that was set on it. Both states can be used at the same time, and the

[PATCH 0/3] Changes to weston to implement the surface states.

From: Rafael Antognolli rafael.antogno...@intel.com Implement the API provided for wayland protocol in a previous patch set. Rafael Antognolli (3): shell: Remove SHELL_SURFACE_MAXIMIZED and use maximized state. shell: Remove SHELL_SURFACE_FULLSCREEN and use fullscreen state. shell:

[PATCH 1/3] shell: Remove SHELL_SURFACE_MAXIMIZED and use maximized state.

From: Rafael Antognolli rafael.antogno...@intel.com Use the newly added maximized state to implement the maximized surface type. Change each place where a surface type change was in place to check for the maximized state too. Setting the surface type to any type should unset the maximized state

[PATCH 2/3] shell: Remove SHELL_SURFACE_FULLSCREEN and use fullscreen state.

From: Rafael Antognolli rafael.antogno...@intel.com Use the newly added fullscreen state to implement the fullscreen surface type. Change each place where a surface type change was in place to check for the fullscreen state too. --- src/shell.c | 108

[PATCH 3/3] shell: Implement state set functions.

From: Rafael Antognolli rafael.antogno...@intel.com The maximized and fullscreen state flags were added, but used only by the original shell_surface_set_maximized and shell_surface_set_fullscreen functions, keeping the previous behavior, removing any other flag that is not the requested one. Now

[PATCH] weston-test-runner: die if parent process dies

From: U. Artie Eoff ullysses.a.e...@intel.com Weston check client tests are fork-exec'd by the Weston process (via the weston-test.so module). If the Weston process dies, the client test might not quit in all cases. This happened in the subsurface-test described at

RE: how to run subsurface-test?

Thanks for your information. -Original Message- From: wayland-devel-bounces+quanxian.wang=intel@lists.freedesktop.org [mailto:wayland-devel-bounces+quanxian.wang=intel@lists.freedesktop.org] On Behalf Of Pekka Paalanen Sent: Monday, June 24, 2013 6:01 PM To: Wang, Quanxian Cc: