From: "U. Artie Eoff"
Signed-off-by: U. Artie Eoff
---
tests/.gitignore| 1 +
tests/Makefile.am | 14 --
tests/button-test.c | 128 +---
3 files changed, 32 insertions(+), 111 deletions(-)
diff --git a/tests/.gitignore b/tests/.gitig
From: "U. Artie Eoff"
Signed-off-by: U. Artie Eoff
---
tests/.gitignore | 1 +
tests/Makefile.am | 31 +--
tests/keyboard-test.c | 139 +++---
3 files changed, 68 insertions(+), 103 deletions(-)
diff --git a/tests/.gitignore b/tes
From: "U. Artie Eoff"
Signed-off-by: U. Artie Eoff
---
tests/.gitignore | 1 +
tests/Makefile.am | 9 +-
tests/event-test.c | 527 +++--
3 files changed, 272 insertions(+), 265 deletions(-)
diff --git a/tests/.gitignore b/tests/.gitignore
From: "U. Artie Eoff"
The weston-tests-env script needs to be able to handle weston
test extension style tests as well as module style tests.
Signed-off-by: U. Artie Eoff
---
tests/Makefile.am | 2 +-
tests/weston-tests-env | 123 -
2 file
From: "U. Artie Eoff"
Add client boiler plate methods to simplify writing tests that use
the weston test extension.
Signed-off-by: U. Artie Eoff
---
tests/weston-test-client-helper.c | 488 ++
tests/weston-test-client-helper.h | 109 +
2 files change
From: "U. Artie Eoff"
Renamed weston-test test environment script to weston-tests-env
to avoid ambiguity with weston-test.c (the weston test extension).
Signed-off-by: U. Artie Eoff
---
tests/Makefile.am | 4 ++--
tests/weston-test | 4
tests/weston-tests-env | 4
3 files c
From: "U. Artie Eoff"
Wayland's test-runner uses a forking method to run each test
in its own address space. This technique works well, thus, do
the same technique for Weston test extension tests.
Signed-off-by: U. Artie Eoff
---
tests/weston-test-runner.c | 114 ++
From: "U. Artie Eoff"
The weston test extension, called weston-test.so, can be loaded
from the "modules" configuration option on the command line
or in the .ini file.
Clients can bind to the "wl_test" interface to interact with
the weston test extension.
Signed-off-by: U. Artie Eoff
---
tests
From: "U. Artie Eoff"
Signed-off-by: U. Artie Eoff
---
protocol/Makefile.am | 3 ++-
protocol/wayland-test.xml | 55 +++
tests/.gitignore | 3 +++
tests/Makefile.am | 9
4 files changed, 69 insertions(+), 1 deletion(-
On 12/04/2012 09:34 PM, Pekka Vuorela wrote:
> On 04.12.2012 00:10, Jan Arne Petersen wrote:
>> +[...]
>> +
>> +if (state == WL_POINTER_BUTTON_STATE_PRESSED)
>> +text_model_invoke_action(entry->model,
>> + button,
>> + cursor - entry->cursor);
On 12/04/2012 09:51 PM, Pekka Vuorela wrote:
> On 30.11.2012 18:01, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
>> Also add a separate preedit-cursor event and add a commit argument to
>> preedit-string to allow to support commit on reset. Fix editor and
>> keyboard example to adapt to
On 12/03/2012 09:26 PM, Pekka Vuorela wrote:
> On ma, 2012-12-03 at 15:15 +0100, Jan Arne Petersen wrote:
>> From: Jan Arne Petersen
>>
>> Support content types in text protocol. Content is defined by a hint
>> bitmask and a purpose field.
>
>> +++ b/protocol/text.xml
>> @@ -83,8 +83,42 @@
>>
On 30.11.2012 18:01, Jan Arne Petersen wrote:
From: Jan Arne Petersen
Also add a separate preedit-cursor event and add a commit argument to
preedit-string to allow to support commit on reset. Fix editor and
keyboard example to adapt to the protocol changes.
[...]
diff --git a/protocol/text.xm
On 04.12.2012 00:10, Jan Arne Petersen wrote:
From: Jan Arne Petersen
Call invoke_action request when a currently composed word is clicked.
Signed-off-by: Jan Arne Petersen
---
clients/editor.c | 52 +---
1 file changed, 41 insertions(+), 11
On Wednesday 2012-10-24 13:51, Pekka Paalanen wrote:
>
>>A few folks around me, and myself included, have pondered...
>>
>>It would seem that wayland and its possible compositors all require
>>3D support, which may require, if no accelerating GPU is installed,
>>the use of software rendering when
After a client has been double-buffering, and then switches to
single-buffering, it should release the 2nd buffer. That never happens
in practice here, so just add a comment and a check in case it ever
occurs in the future.
If we implemented the releasing now, it would be difficult to test.
Signe
Plug an insignificant memory leak in demo programs that bother to clean
up at all.
Signed-off-by: Pekka Paalanen
---
clients/simple-egl.c |1 +
clients/simple-shm.c |1 +
clients/window.c |1 +
3 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/clients/simple-egl.c b/
Only the gl_renderer uses this field.
Signed-off-by: Pekka Paalanen
---
src/compositor.c |3 ---
src/compositor.h |1 -
src/gl-renderer.c | 15 +--
3 files changed, 9 insertions(+), 10 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index 6e58776..f56e515 1
It is not used by anything but the gl-renderer.
Signed-off-by: Pekka Paalanen
---
src/compositor.c |1 -
src/compositor.h |1 -
src/gl-renderer.c | 21 ++---
3 files changed, 14 insertions(+), 9 deletions(-)
diff --git a/src/compositor.c b/src/compositor.c
index 38bc
A client can reliably avoid allocating a second buffer per surface, if
the compositor sends the wl_buffer.release event before the frame
callback. To enable clients' single-buffering, release the wl_buffer
early if possible. Otherwise clients will double-buffer.
Releasing early is not possible, if
Instead of relying on the compositor core to keep the wl_buffer around
and unreleased, take a new reference to it in gl-renderer. This makes
sure in the future, that the gl-renderer always has the buffer at hand,
client misbehaviour excluded.
The reference is taken in the attach callback, and rele
The wl_buffer reference counting API has been inconsistent. You would
manually increment the refcount and register a destroy listener, as
opposed to calling weston_buffer_post_release(), which internally
decremented the refcount, and then removing a list item.
Replace both cases with a single func
The protocol does not require us to flush_damage() on wl_buffer
destruction. In fact, by the time the server receives this request, the
client may have already clobbered the buffer's storage, so we could be
reading undefined data. Instead, just forget about the buffer. The
protocol already says, th
If a client called wl_surface.attach with the same wl_buffer as
previously, the compositor would mistakenly send a release on that
buffer. This will cause problems only when clients start to properly use
the wl_buffer.release event.
Do not send wl_buffer.release if the same buffer is attached agai
Hi Kristian,
this is the rebased and modifed version of the server side
wl_buffer.release series.
Changes since v1:
- rebased
- added struct weston_buffer_reference to consolidate
the destroy handler functions
- shm flush on destroy is now a separate patch instead of in
the gl patch
- compositor-
From: Rob Bradford
The rebase seemed to break this.
---
shared/Makefile.am | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/shared/Makefile.am b/shared/Makefile.am
index 90d8ed6..faf073d 100644
--- a/shared/Makefile.am
+++ b/shared/Makefile.am
@@ -7,7 +7,9 @@ libshared
This patch should be squashed with "Move matrix.[ch] to shared"
___
wayland-devel mailing list
wayland-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
On Mon, 3 Dec 2012 19:02:06 -0500
David Jackson wrote:
> With Wayland will we be able to:
>
> Have multiple seperate wayland sessions on the same computer, as many as
> one wishes,
Yes.
> with many of them being headless, accessible if the user wishes
> through a remote desktop solution such a
On Mon, 3 Dec 2012 20:45:14 +
Keller Alexander-B42067 wrote:
> I have been trying to get my touchscreen inputs to work on Wayland, and
> everytime the screen is touched I get an error saying "couldn't find
> resource." I get that error because my seat->touch->resource_list is empty,
> and
29 matches
Mail list logo
