Hi I have been away for a while and quite busy so I did not get a
chance to response.
On Tue, Apr 28, 2015 at 3:46 AM, Bill Spitzak wrote:
> No, I absolutely 100% disagree.
>
> Synchronized updating so things don't vibrate or shift is more important
> than FPS. It is even stated as part of Waylan
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation,
Following features are tested,
- add notification of ivi-layer with bad parameter
- add notification of ivi-surface configure with bad parameter
- add notification of creating i
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- add notfication of ivi-surface with bad condition
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
tests/ivi_layout-test-plugin.c | 22 ++
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested,
- notification of adding ivi-layer
- notification of creating ivi-layer
- notification of removing ivi-layer
Signed-off-by: Nobuhiko Tanibata
Re
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- notification of adding ivi-surface
- notification of ivi-surface configure
- notification of creating ivi-surface
- notification of removing ivi-surf
From: Nobuhiko Tanibata
The TESTs in ivi_layout-test.c may have several server-side parts
(RUNNER_TEST in ivi_layout-test-plugin.c) each. Sometimes we need to
carry state from one RUNNER_TEST to another within one TEST, but not
across multiple TESTs. The correct lifetime of that state would be th
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation,
Following features are tested,
- ivi-screen operation with bad parameter
- render order with bad parameter
- destroy ivi-layer in the ivi-screen and call commit_changes
Signed-
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested,
- ivi-screen id
- ivi-screen resolution
- render order of ivi-layers in ivi-screen
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested for ivi-layer,
- create with bad parameter
- visibility with bad parameter
- opacity with bad parameter
- destination rectangle with bad parameter
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- bad render order of ivi-surface on ivi-layer
- call commitchanges after a ivi_surface in render order is destoryed
Signed-off-by: Nobuhiko Tanibata
Reviewe
From: Nobuhiko Tanibata
These test are implemented on test suite framework, which provides
helper client.
Following features are tested,
- render order of ivi-surfaces on ivi-layer
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
tests/ivi-test.h | 4
tests
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested for ivi-layer,
- create
- visibility
- opacity
- orientation
- dimension
- position
- destination rectangle
- source rectangle
Signed-off-by: Nobu
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
internal method validation.
Following features are tested for ivi-surface,
- destination_rectangle with bad parameter
- orientation with bad parameter
- dimension with bad parameter
- position with bad par
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested for ivi-surface
- orientation
- dimension
- position
- destination rectangle
- source rectangle
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
From: Nobuhiko Tanibata
These tests are implemented on test suite framework, which provides
helper client.
Following features are tested,
- ivi_layout_runner with basic_test_names[]
- surface with bad opacity
- destroy ivi/wl_surface and call get_surface
- commit_changes_after_properties_set_sur
From: Nobuhiko Tanibata
"remove" is not proper name beacause it destorys a layer. The name of
the api is changed from layer_remove to layer_destroy.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/ivi-layout-export.h | 2 +-
ivi-shell/ivi-layout.c| 4 ++--
2
From: Nobuhiko Tanibata
To get property changes of ivi_layer, callbacks can be registered.
However there was no API to remove a callback rather than removing all
callbacks by using layer_remove_notification.
layer_remove_notification_by_callback can do it.
Signed-off-by: Nobuhiko Tanibata
Acked
From: Nobuhiko Tanibata
In previous code, it sends notification whenever setter calls. This
patch fixs that notification will not happens if there is no change of
properties by setter.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 80 +++
From: Nobuhiko Tanibata
This interface is required for user to manage screens per IDs.
Signed-off-by: Nobuhiko Tanibata
Acked-by: Pekka Paalanen
---
ivi-shell/ivi-layout-export.h | 7 +++
ivi-shell/ivi-layout.c| 15 +--
2 files changed, 20 insertions(+), 2 deletions(-
From: Nobuhiko Tanibata
Previous code sends notification without event mask. So the notification
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell
From: Nobuhiko Tanibata
To get property changes of ivi_surface, callbacks can be registered.
However there was no API to remove a callback rather than remove all
callbacks by using surface_remove_notification.
surface_remove_notification_by_callback can do it.
Signed-off-by: Nobuhiko Tanibata
A
From: Nobuhiko Tanibata
if a controller calls ivi_layout_layer_create_with_demenstion with a ID
which is already created before, the API returns exist ivi_layer.
However addtionally, it shall count up ref count to destroy ivi_layer
when ref count is 0. The previous code will destroy ivi_layer
imm
From: Nobuhiko Tanibata
ivi_shell_surface lifetime shall follow the ivi_surface protocol object
lifetime, and frees the ivi-id by destroying the ivi_layout_surface
from both wl_surface and ivi_surface destruction as the protocol specifies.
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paa
From: Nobuhiko Tanibata
Signed-off-by: Nobuhiko Tanibata
Acked-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c
index 7bc3aab..2cce2d3 100644
--- a/ivi-shell/ivi-layout.c
+++ b/ivi-
From: Nobuhiko Tanibata
Signed-off-by: Nobuhiko Tanibata
Reviewed-by: Pekka Paalanen
---
ivi-shell/ivi-layout-private.h | 3 ++-
ivi-shell/ivi-layout.c | 54 --
ivi-shell/ivi-shell.c | 26 +---
3 files changed, 35 insert
From: Nobuhiko Tanibata
Signed-off-by: Nobuhiko Tanibata
Acked-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c
index 50ce22f..88629ad 100644
--- a/ivi-shell/ivi-layout.c
+++ b/i
From: Nobuhiko Tanibata
Signed-off-by: Nobuhiko Tanibata
Acked-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c
index 88629ad..7bc3aab 100644
--- a/ivi-shell/ivi-layout.c
+++ b/ivi-
From: Nobuhiko Tanibata
Signed-off-by: Nobuhiko Tanibata
Acked-by: Pekka Paalanen
---
ivi-shell/ivi-layout.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/ivi-shell/ivi-layout.c b/ivi-shell/ivi-layout.c
index 4aed4c8..50ce22f 100644
--- a/ivi-shell/ivi-layout.c
+++ b/i
Hi,
I am proposing a set of patches; ivi-shell test suite and bug fixes
found
by these test cases. This test suite is implemented based on following
test
framework.
http://lists.freedesktop.org/archives/wayland-devel/2015-March/020932.html
This test suite consists of four parts to verify ivi-
Signed-off-by: Peter Hutterer
---
test/touchpad-tap.c | 57 +++--
1 file changed, 51 insertions(+), 6 deletions(-)
diff --git a/test/touchpad-tap.c b/test/touchpad-tap.c
index 9bc02a0..d04feb4 100644
--- a/test/touchpad-tap.c
+++ b/test/touchpad-ta
Signed-off-by: Peter Hutterer
---
tools/event-debug.c | 7 ++-
tools/shared.c | 16
tools/shared.h | 1 +
3 files changed, 23 insertions(+), 1 deletion(-)
diff --git a/tools/event-debug.c b/tools/event-debug.c
index 7aeac06..becde16 100644
--- a/tools/event-debug
A new release of libinput, 0.18.0, is now available.
Touchpad handling has improved filters for erroneous small movements.
Palm detection in the edge scrolling zone has been disabled, it previously
caused unreliable edge scrolling on larger touchpads.
Alps touchpads now always provide a config o
No functional change, other than that we check for status codes now too.
In tests that don't specifically check the interface itself, a short
enable_tap() or disable_tap() is a lot more obvious to parse for the reader.
Signed-off-by: Peter Hutterer
---
test/litest.h | 24
tes
In some applications, notably Inkscape, where it is common to frequently drag
objects a short distance the default to drag-lock always-on is frustrating for
users.
Make it configurable, with the current default to "on".
New API:
libinput_device_config_tap_set_drag_lock_enabled
libinput_device_c
Multiple devices plugged into the same USB hub have the same
PHYS path and are assigned to the same group.
Prepend the content of the PRODUCT env to the phys path, this at least ensures
that different devices are never grouped together.
https://bugs.freedesktop.org/show_bug.cgi?id=89802
Signed-o
On Fri, Jun 19, 2015 at 03:24:38PM +0200, Andreas Pokorny wrote:
> This change adds four new properties to touch events.
> major: diameter of the touch ellipse along the major axis
> minor: diameter perpendicular to major axis
> pressure: a pressure value mapped into the range [0,1]
> orientation:
If a stopped repaint loop gets restarted due to posting of new
damage, and this restart of the repaint loop happens late in the
video refresh cycle, ie. already inside the repaint-window and
thereby after the composition deadline for the current frame,
then defer the actual output repaint to the co
The matching logic in choose_mode() compared refresh rate
of a drm_mode candidate mode expressed in Hz against the
requested refresh rate of the target weston_mode expressed
in milliHz, so the match always failed and the logic always
ended up the mode with the highest refresh rate for a given
resol
Allows to force loading an identity gamma table if
option icc_profile=identity is given in weston.ini for
an output.
Some special display output devices, e.g., for
neuro-science applications, and special display
testing hardware need a guaranteed perfect pixel
passthrough from framebuffer to outpu
drm_output_start_repaint_loop() incurred a delay of
one refresh cycle by using a no-op page-flip to get
an accurate vblank timestamp as reference. This causes
unwanted lag whenever Weston exited its repaint loop, e.g.,
whenever an application wants to repaint with less than
full video refresh rate
cms-colord used the weston_compositor destroy signal to
trigger its final colord_module_destroy cleanup, and the
wl_output destroy signal to trigger per output cleanup.
The problem is that the compositor destroy signal gets
emitted before the output destroy signals at compositor
shutdown, colord_m
Initialize output->native_mode with the initially chosen
mode for an output, so weston_output_mode_switch_to_native()
has something to work with and can switch back from temporary
selected modes to the outputs native mode. Before, this was a
no-op.
This allows an output to switch back to its defau
A new optional parameter "-d msecs" allows to specify a
delay before the surface attach/damage/commit to shift
the point in time when a surface update is committed.
This allows to test how different client timings interact
with the compositors repaint timing.
Suggested by Pekka Paalanen.
Signed-
Hi,
now that weston 1.8 is out, i'm resending my series with bug
fixes. Difference to the previous series:
Patch 03: Removed a redundant/confusing weston_log debug message.
All patches: Rebased onto current master to fix conflicts caused
by some white-space changes in current master/weston-1.8.
Allow proper handling of output->pipe > 1 to support
triple-head graphics cards etc. by using the "high-crtc"
support introduced in Linux 2.6.39 and libdrm 2.4.25
around May 2011.
Signed-off-by: Mario Kleiner
---
src/compositor-drm.c | 14 --
1 file changed, 12 insertions(+), 2 delet
Fix desktop-shell's activate() method to only restore the output
mode on the single output on which a shell surface gets activated.
This way toplevel fullscreen surfaces can mode-switch their output
via method WL_SHELL_SURFACE_FULLSCREEN_METHOD_DRIVER and that
temporary mode properly persists unti
Desktop shell demoted all fullscreen shell surfaces on all active
outputs of a multi-display setup whenever any shell surface was
activated anywhere. This made it impossible to have multiple
fullscreen windows on separate outputs active at the same
time, as creating or activating any shell surface
On 2015-06-21 00:47, Jon A. Cruz wrote:
> diff --git a/configure.ac b/configure.ac
> index e047fd5..4a89819 100644
> --- a/configure.ac
> +++ b/configure.ac
> @@ -264,6 +264,11 @@ if test "x$cairo_modules" = "xcairo-glesv2"; then
> AC_DEFINE([USE_CAIRO_GLESV2], [1], [Use the GLESv2 GL cairo backen
48 matches
Mail list logo