From: Pekka Paalanen pekka.paala...@collabora.co.uk
After the update, you get the latest xserver branch, which at the time
of writing is based on xserver 1.14.99.
You also get the latest xf86-video-wayland, which was renamed from
xf86-video-wlshm.
---
Hi,
is there any reason to not have these
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Tue, 10 Dec 2013 15:55:29 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
if a surface has not a buffer yet and a weston_view gets created for
it, the surface's width and height will be 0 and the view's
output_mask will be 0, because the
On Wed, 11 Dec 2013 11:23:50 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Tue, 10 Dec 2013 15:55:29 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
if a surface has not a buffer yet and a weston_view gets created
for it, the
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Wed, 11 Dec 2013 11:23:50 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Tue, 10 Dec 2013 15:55:29 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
if a surface has not a buffer
On Wed, 11 Dec 2013 12:20:41 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Wed, 11 Dec 2013 11:23:50 +0100
Giulio Camuffo giuliocamu...@gmail.com wrote:
2013/12/11 Pekka Paalanen ppaala...@gmail.com:
On Tue, 10 Dec 2013 15:55:29
Another neat option would be to include blah_blah.c files (with static
function definitions u want to test) into blah_blah-test.c files. I like
this solution more than macro redefinitions as it's simpler and lets you
call actually static functions which makes testing stricter (just a little
bit :)
Hi Emilio,
On Dec 9, 2013 6:38 AM, Emilio Pozuelo Monfort poch...@gmail.com wrote:
Hi,
I was looking at making gtk+ try the wayland backend before the x11 one
[1].
This would solve the problem where every gtk+ app uses the x11 backend
through
XWayland when the latter is available.
As you
this adds a mechanism to mask the views belonging to a layer
to an arbitrary rect, in the global space. The parts that don't fit
in that rect will be clipped away.
Implemented in the gl and pixman renderers, while it needs to be
implemented in the rpi renderer.
---
v3: no new code. added a
Wayland doesn't have a way to inject mouse events currently. Some
protocol must be written, which would be presumably implemented as a
private protocol which only trusted clients can use, given the
security implications.
Giulio
2013/12/10 Piñeiro apinhe...@igalia.com:
GNOME Assistive
Not currently.
I'm not sure what you mean with consumed. Do you mean that a not
consumed event is still received by the client that has the focus
while a consumed one is not?
If so, i guess a protocol could be developed where the compositor
sends an event with the key that is pressed and then the
On 12/11/2013 07:14 PM, Giulio Camuffo wrote:
Not currently.
I'm not sure what you mean with consumed. Do you mean that a not
consumed event is still received by the client that has the focus
while a consumed one is not?
Yes, means that. On the example with Orca (GNOME screen reader), if you
On 12/11/2013 07:09 PM, Giulio Camuffo wrote:
Wayland doesn't have a way to inject mouse events currently. Some
protocol must be written, which would be presumably implemented as a
private protocol which only trusted clients can use, given the
security implications.
I was guessing about
I certainly like that there is a fallback. The user should not have to
set environment variables to get something to work.
In our software using X we always check if DISPLAY is set and if not set
it to :0. This is so the program just works even if the user's setup
is wrong. (The primary
Piñeiro wrote:
On 12/11/2013 07:14 PM, Giulio Camuffo wrote:
Not currently.
I'm not sure what you mean with consumed. Do you mean that a not
consumed event is still received by the client that has the focus
while a consumed one is not?
Yes, means that. On the example with Orca (GNOME screen
---
desktop-shell/shell.c | 2 ++
src/compositor.c | 1 -
src/screenshooter.c | 2 +-
3 files changed, 3 insertions(+), 2 deletions(-)
diff --git a/desktop-shell/shell.c b/desktop-shell/shell.c
index 9fbac00..520623f 100644
--- a/desktop-shell/shell.c
+++ b/desktop-shell/shell.c
@@
This allows other screenshooter protocols to use the same code to copy
the screen to a buffer.
---
src/compositor.h| 12
src/screenshooter.c | 82 +
2 files changed, 70 insertions(+), 24 deletions(-)
diff --git a/src/compositor.h
Instead of using the surface size, save the last known shell surface
size, and use that one to emit on configure, when the surface is
returning from maximized or fullscreen state.
The surface size can't be saved because it will have already changed
when the surface is transitioning to fullscreen
On Wed, Dec 11, 2013 at 2:15 PM, Piñeiro apinhe...@igalia.com wrote:
On 12/11/2013 07:09 PM, Giulio Camuffo wrote:
Wayland doesn't have a way to inject mouse events currently. Some
protocol must be written, which would be presumably implemented as a
private protocol which only trusted
On Tue, Dec 10, 2013 at 3:29 PM, Piñeiro apinhe...@igalia.com wrote:
GNOME Assistive Technologies need to be able to listen to key events
globally and have the possibility of consuming them. Example use
cases:
* Orca's presentation of navigation (Events not consumed)
- Right Arrow: Speak
19 matches
Mail list logo
