Since it's the server who moves the surface it's the server who sets the
pointer image.
Signed-off-by: Jonas Ådahl
---
clients/window.c |1 -
1 file changed, 1 deletion(-)
diff --git a/clients/window.c b/clients/window.c
index 118dce5..8aeb837 100644
--- a/clients/window.c
+++ b/clients/win
Motion handlers are called for either grabbed or focused widgets. If a
menu is displayed, thus grabbed, motion events relative to the parent
surface are delivered to the menu widget motion handler even though it
is not in focus. By checking that the menu widget is the focused one we
can avoid setti
On 10/18/2012 01:48 PM, Kristian Høgsberg wrote:
> On Thu, Oct 18, 2012 at 4:27 PM, David Herrmann
> wrote:
>> Hi Chad
>>
>> On Thu, Oct 18, 2012 at 9:45 PM, Chad Versace
>> wrote:
>>> On 10/18/2012 12:35 PM, Chad Versace wrote:
On 10/18/2012 10:23 AM, Pekka Paalanen wrote:
> On Thu, 18
On Thu, Oct 18, 2012 at 2:46 PM, Keller Alexander-B42067 <
b42...@freescale.com> wrote:
> I am new to using the Wayland API, and I was just wondering about the
> seat structure. I was reading the documentation on the Wayland website and
> read that the seat structure takes care of device events a
I am new to using the Wayland API, and I was just wondering about the seat
structure. I was reading the documentation on the Wayland website and read that
the seat structure takes care of device events and maintains device focus.
(such as the keyboard, touch, and pointer) My question is what f
On Thu, Oct 18, 2012 at 4:27 PM, David Herrmann
wrote:
> Hi Chad
>
> On Thu, Oct 18, 2012 at 9:45 PM, Chad Versace
> wrote:
>> On 10/18/2012 12:35 PM, Chad Versace wrote:
>>> On 10/18/2012 10:23 AM, Pekka Paalanen wrote:
On Thu, 18 Oct 2012 09:15:08 -0700
Chad Versace wrote:
>
Hi Chad
On Thu, Oct 18, 2012 at 9:45 PM, Chad Versace
wrote:
> On 10/18/2012 12:35 PM, Chad Versace wrote:
>> On 10/18/2012 10:23 AM, Pekka Paalanen wrote:
>>> On Thu, 18 Oct 2012 09:15:08 -0700
>>> Chad Versace wrote:
>>>
wayland-util.h defined an unprefixed macro, ARRAY_LENGTH, which poll
On 10/18/2012 12:35 PM, Chad Versace wrote:
> On 10/18/2012 10:23 AM, Pekka Paalanen wrote:
>> On Thu, 18 Oct 2012 09:15:08 -0700
>> Chad Versace wrote:
>>
>>> wayland-util.h defined an unprefixed macro, ARRAY_LENGTH, which polluted
>>> the global namespace. This caused symbol collisions in projec
On 10/18/2012 10:23 AM, Pekka Paalanen wrote:
> On Thu, 18 Oct 2012 09:15:08 -0700
> Chad Versace wrote:
>
>> wayland-util.h defined an unprefixed macro, ARRAY_LENGTH, which polluted
>> the global namespace. This caused symbol collisions in projects that
>> defined ARRAY_LENGTH slightly different
On Thu, 18 Oct 2012 09:15:08 -0700
Chad Versace wrote:
> wayland-util.h defined an unprefixed macro, ARRAY_LENGTH, which polluted
> the global namespace. This caused symbol collisions in projects that
> defined ARRAY_LENGTH slightly differently.
>
> Signed-off-by: Chad Versace
Hi Chad,
do you
wayland-util.h defined an unprefixed macro, ARRAY_LENGTH, which polluted
the global namespace. This caused symbol collisions in projects that
defined ARRAY_LENGTH slightly differently.
Signed-off-by: Chad Versace
---
cursor/wayland-cursor.c | 2 +-
src/connection.c| 6 +++---
src/event
wayland-util.h defined two variants of the container_of macro:
__wl_container_of() and an unprefixed container_of(). The unprefixed
variant, of course, polluted the global namespace and caused symbol
collisions in projects that defined container_of slightly differently.
This patch removes the defi
On 10/17/2012 11:53 PM, Kristian Høgsberg wrote:
On Wed, Oct 17, 2012 at 01:49:08PM +0300, Ander Conselvan de Oliveira wrote:
Argh, thanks. I don't get a warning about ret being unused, and I did
check the -Wall was in the compiler flags...
I'm not really sure, but it looks like
http://gcc
13 matches
Mail list logo
