[Xcb] xcb-xinput -- raw motion events

Ingo Bürk admin at airblader.de
Mon May 25 23:31:39 PDT 2015


Hi Chris,

thanks for your answer. Unfortunately, this would require anyone using
my project to use the git version as well :(
Maybe I just have to fall back to using Core Protocol for my event loop
and abstract my handlers from XLib/XCB. That should hopefully work.


Ingo

On 05/26/2015 06:54 AM, chris at demorecorder.com wrote:
> Hi Ingo,
>
> For XInput, I suggest that you use the current HEAD from git 
>    http://cgit.freedesktop.org/xcb/proto
>    http://cgit.freedesktop.org/xcb/libxcb
>
> The reason is that in the previous official version, xinput is not officially supported 
> and contains a lot of bugs and missing pieces, most of which are fixed in the git-HEAD.
>
> That may be the reason why you weren't able to figure it out.
>
> Hope this helps,
>
> Chris
>
> Ingo Bürk wrote on 25.05.2015 23:40:
>
> Hi,
>> I want to receive all (raw) motion events on a window for which I am trying to use xcb-xinput.
>> Unfortunately, I can't seem to figure out how to use it. I found the Xlib equivalent[1], but am unable to translate it to xcb. Would someone mind giving me a small push on how I can set XCB_INPUT_XI_EVENT_MASK_RAW_MOTION on a window?
>>
>> Addendum / Additional Info: I am currently using XCB_EVENT_MASK_POINTER_MOTION, but it seems that selecting motion events on children of Chromium windows break Chromium[2] (wtf), so my hope is that using XInput would work around this issue.
>>
>>
>> Thanks!
>> Ingo
>>
>> [1] http://keithp.com/blogs/Cursor_tracking/ <http://keithp.com/blogs/Cursor_tracking/> 
>> [2] https://code.google.com/p/chromium/issues/detail?id=491934 <https://code.google.com/p/chromium/issues/detail?id=491934>



More information about the Xcb mailing list