On Tue, 10 Dec 2013 15:55:29 +0100
Giulio Camuffo 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 surface's area is 0. Later commits
> on the surface with valid buffers
On Tue, 10 Dec 2013 16:09:18 +0100
Giulio Camuffo wrote:
> 2013/12/10 Pekka Paalanen :
> > On Tue, 10 Dec 2013 14:46:25 +0100
> > Giulio Camuffo wrote:
> >
> >> But the visible region of a surface wouldn't be a rect minus a
> >> rect, but the intersection of two rects, which is always a rect as
Am 2013-12-10 00:20, schrieb Bryce W. Harrington:
On Wed, Dec 04, 2013 at 05:38:23PM +0100, Sebastian Wick wrote:
This patch adds a screenshooter section with the "restrict-access"
setting which is on by default and is the current behavior of weston.
When turning it off, all clients can use the
On 10/12/2013, Giulio Camuffo 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 surface's area is 0. Later commits on the surface
with valid buffers will then trigger a surfac
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 character moved to (right of cursor)
- Shift Right Arrow: Speak character
GNOME Assistive Technologies need to be able to synthesize mouse events.
Use cases:
* Perform a mouse button click for users who cannot use a physical mouse
* Route the mouse pointer to an object or element to trigger its hover
action
The Orca screen reader currently provides these commands vi
This introduces a new struct, weston_layer_entry, which is now used
in place of wl_list to keep the link for the layer list in weston_view
and the head of the list in weston_layer.
weston_layer_entry also has a weston_layer*, which points to the layer
the view is in or, in the case the entry it's t
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 only for now.
---
v2: do the masking in the renderers
src/compositor.c | 26
2013/12/10 Pekka Paalanen :
> On Tue, 10 Dec 2013 14:46:25 +0100
> Giulio Camuffo wrote:
>
>> But the visible region of a surface wouldn't be a rect minus a rect,
>> but the intersection of two rects, which is always a rect as long as
>> they are both axis aligned, and surface rotation isn't suppo
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 surface's area is 0. Later commits on the surface
with valid buffers will then trigger a surface repaint, which will do
nothing because
On Tue, 10 Dec 2013 14:46:25 +0100
Giulio Camuffo wrote:
> But the visible region of a surface wouldn't be a rect minus a rect,
> but the intersection of two rects, which is always a rect as long as
> they are both axis aligned, and surface rotation isn't supported
> anyway by the rpi renderer, r
But the visible region of a surface wouldn't be a rect minus a rect,
but the intersection of two rects, which is always a rect as long as
they are both axis aligned, and surface rotation isn't supported
anyway by the rpi renderer, right? What's a rect minus a rect is the
weston_view::clip region, w
On Tue, 10 Dec 2013 14:13:50 +0100
Giulio Camuffo wrote:
> 2013/12/10 Pekka Paalanen :
> > On Tue, 10 Dec 2013 11:13:42 +0100
> > Giulio Camuffo wrote:
> >
> >> 2013/12/10 Jason Ekstrand :
> >> > Giulio,
> >> > Couple thoughts. First, you don't provide an implementation of
> >> > the clipping i
2013/12/10 Pekka Paalanen :
> On Tue, 10 Dec 2013 11:13:42 +0100
> Giulio Camuffo wrote:
>
>> 2013/12/10 Jason Ekstrand :
>> > Giulio,
>> > Couple thoughts. First, you don't provide an implementation of the
>> > clipping in any of the renderers. Probably have to wait on the
>> > Collabora peopl
On Tue, 10 Dec 2013 11:13:42 +0100
Giulio Camuffo wrote:
> 2013/12/10 Jason Ekstrand :
> > Giulio,
> > Couple thoughts. First, you don't provide an implementation of the
> > clipping in any of the renderers. Probably have to wait on the
> > Collabora people for the RPi renderer, but we should
From: Quentin Glidic
AC_SEARCH_LIBS is preferred over AC_CHECK_FUNC and AC_CHECK_LIB
See
http://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf.html#Libraries
AC_SEARCH_LIBS is doing precisely the double checking we used to have
for dlopen
Introduce WS_SEARCH_LIBS to make it easier f
On 10/12/2013 10:57, Ander Conselvan de Oliveira wrote:
On 12/09/2013 12:44 PM, Quentin Glidic wrote:
On 09/12/2013 11:28, Ander Conselvan de Oliveira wrote:
I am trusting the Autoconf manual[1] on this one. Basically, the
double-check we are doing for dlopen is exactly what AC_SEARCH_LIBS is
do
2013/12/10 Jason Ekstrand :
> Giulio,
> Couple thoughts. First, you don't provide an implementation of the clipping
> in any of the renderers. Probably have to wait on the Collabora people for
> the RPi renderer, but we should have pixman and gl implementations of this.
There is no need to add
On 10/12/2013 09:25, Hardening wrote:
On 10/12/2013 00:42, Kristian Høgsberg wrote:
On Mon, Dec 09, 2013 at 10:16:39PM +0100, Hardening wrote:
The API to use remoteFx encoding has changed between master and
stable 1.1
branch. This patch fixes compilation for both.
Please note that the freerdp/
On 12/09/2013 12:44 PM, Quentin Glidic wrote:
On 09/12/2013 11:28, Ander Conselvan de Oliveira wrote:
On 12/08/2013 08:45 PM, Quentin Glidic wrote:
From: Quentin Glidic
AC_SEARCH_LIBS is preferred over AC_CHECK_FUNC and AC_CHECK_LIB
Why is it preferred?
I am trusting the Autoconf manual[1
Hi Nobuhiko-san,
I want to provide some feedback from GENIVI and IVI LayerManagement perspective.
Please find my comments inline.
BR, Timo
--
BMW Car IT GmbH
Timo Lotterbach
Spezialist Entwicklung
Petuelring 116
80809 München
Tel.: +49 89 189311-77
Fax: +49 89 189311-20
Mail: timo.lotterb...@
Hi,
For me mmap capability means that both server and client can call
mmap() on the provided file descriptor.
I have no simple way to know if the driver support mmap().
The better option I see today is to create a dumb buffer and to try to
mmap it at server initialization.
Anyway client and server
On 10/12/2013 00:42, Kristian Høgsberg wrote:
On Mon, Dec 09, 2013 at 10:16:39PM +0100, Hardening wrote:
The API to use remoteFx encoding has changed between master and stable 1.1
branch. This patch fixes compilation for both.
Please note that the freerdp/version.h file is generated in the very
23 matches
Mail list logo
