On Thu, Oct 18, 2012 at 6:52 PM, Chad Versace
wrote:
> 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 Fri, Oct 19, 2012 at 07:56:02PM +0200, Jonas Ådahl wrote:
> Grabbed widgets should always receive motion events as if it was the
> widget that would receive it if no grab was active. This means that the
> focused widget should always be passed as the widget argument to widget
> motion handlers.
On Fri, Oct 19, 2012 at 06:29:54PM +0300, Tiago Vignatti wrote:
> Fix https://bugs.freedesktop.org/show_bug.cgi?id=56101
Thanks, applied.
Kristian
> Signed-off-by: Tiago Vignatti
> ---
> configure.ac |8
> 1 file changed, 8 insertions(+)
>
> diff --git a/configure.ac b/configure.
On Fri, Oct 19, 2012 at 03:30:25PM +0300, Ander Conselvan de Oliveira wrote:
> Clarify on what cases each of the dispatching functions may block, what
> is the main thread and add some real world examples.
> ---
>
> Hi Kristian,
>
> Hopefully I got it right this time. The documentation for
> wl_d
Grabbed widgets should always receive motion events as if it was the
widget that would receive it if no grab was active. This means that the
focused widget should always be passed as the widget argument to widget
motion handlers.
This reverts commit 8c9c8fcf6e294f0446446d8e9bdfeb37294743c3.
Signe
Fix https://bugs.freedesktop.org/show_bug.cgi?id=56101
Signed-off-by: Tiago Vignatti
---
configure.ac |8
1 file changed, 8 insertions(+)
diff --git a/configure.ac b/configure.ac
index 1c102c6..1a10cf8 100644
--- a/configure.ac
+++ b/configure.ac
@@ -86,6 +86,14 @@ if test "x$enabl
---
doc/doxygen/Makefile.am |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/doc/doxygen/Makefile.am b/doc/doxygen/Makefile.am
index 76f4cf6..957aa3d 100644
--- a/doc/doxygen/Makefile.am
+++ b/doc/doxygen/Makefile.am
@@ -2,7 +2,11 @@
noinst_DATA = xml/index.xml
dist_no
Clarify on what cases each of the dispatching functions may block, what
is the main thread and add some real world examples.
---
Hi Kristian,
Hopefully I got it right this time. The documentation for
wl_display_dispatch_pending() is pretty much a reword of your answer
to my previous patch.
Feel
On Fri, Oct 19, 2012 at 1:10 PM, Pekka Vuorela wrote:
> 2012/10/19 Jonas Ådahl :
>> 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
2012/10/19 Jonas Ådahl :
> 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 t
10 matches
Mail list logo