On 01/-10/-28163 11:59 AM, Christopher Michael wrote:
On 12/08/11 10:14, Tiago Vignatti wrote:
Hi, sorry for late reply.
On 11/29/2011 08:30 PM, Christopher Michael wrote:
I found an issue while working on some local code, that may be a bug in
the input handling of Wayland.
<<< big snip >>>
On 12/08/11 18:01, Tiago Vignatti wrote:
On 12/08/2011 09:34 PM, Christopher Michael wrote:
On 12/08/11 10:14, Tiago Vignatti wrote:
Hi, sorry for late reply.
On 11/29/2011 08:30 PM, Christopher Michael wrote:
I found an issue while working on some local code, that may be a bug in
the input
On 12/08/2011 09:34 PM, Christopher Michael wrote:
On 12/08/11 10:14, Tiago Vignatti wrote:
Hi, sorry for late reply.
On 11/29/2011 08:30 PM, Christopher Michael wrote:
I found an issue while working on some local code, that may be a bug in
the input handling of Wayland.
In my function to pr
On 12/08/11 10:14, Tiago Vignatti wrote:
Hi, sorry for late reply.
On 11/29/2011 08:30 PM, Christopher Michael wrote:
I found an issue while working on some local code, that may be a bug in
the input handling of Wayland.
In my function to process button events (from mouse), the 'btn'
paramete
Hi, sorry for late reply.
On 11/29/2011 08:30 PM, Christopher Michael wrote:
I found an issue while working on some local code, that may be a bug in
the input handling of Wayland.
In my function to process button events (from mouse), the 'btn'
parameter that gets returned to my handler seems i
Hi All,
I found an issue while working on some local code, that may be a bug in
the input handling of Wayland.
In my function to process button events (from mouse), the 'btn'
parameter that gets returned to my handler seems incorrect for Wheel Events.
Basically, mouse wheel down events are
