=== alan_g is now known as alan_g|lunch
=== ara is now known as Guest94549
=== chunsang is now known as chunsang-away
[13:34] <mlankhorst> greyback: so did you take a look yet why I get touch events instead of pointer events?
[13:36] <greyback> mlankhorst: with mir alone, or with unity8?
[13:39] <mlankhorst> unity8 only
[13:39] <mlankhorst> nested mir works normally
=== alan_g|lunch is now known as alan_g
[13:57] <greyback> mlankhorst: ok, is because qtmir forwards on all input events as touch events - even if they started as mouse. Should be fixed by https://code.launchpad.net/~mir-team/qtmir/port-to-event-2.0/+merge/248067
[13:59] <mlankhorst> oke
[14:00] <mlankhorst> ah new version
=== chunsang-away is now known as chunsang
[14:31] <mlankhorst> greyback: are you sure it works? i apply it from r310 onward onto my qtmir snapshot from the 0.11 ppa and I still don't get touch events
[14:31] <greyback> mlankhorst: I've tested it with Qt stuff, it appeared to work ok.
[14:34] <mlankhorst> do you recompile anything else?
[14:34] <greyback> nope
[14:35] <mlankhorst> hm what version of mir do you use? trying from the port-to-event one I get /QtSensors    -o CMakeFiles/unityapplicationplugin.dir/mirsurfaceitem.cpp.o -c /home/mlankhorst/nfs/xorg/port-to-event-2.0/src/modules/Unity/Application/mirsurfaceitem.cpp
[14:36] <mlankhorst> /home/mlankhorst/nfs/xorg/port-to-event-2.0/src/modules/Unity/Application/mirsurfaceitem.cpp: In member function ‘bool qtmir::MirSurfaceItem::updateTexture()’:
[14:36] <mlankhorst> /home/mlankhorst/nfs/xorg/port-to-event-2.0/src/modules/Unity/Application/mirsurfaceitem.cpp:396:21: error: ‘class mir::graphics::Renderable’ has no member named ‘buffers_ready_for_compositor’
[14:36] <mlankhorst>      if (renderable->buffers_ready_for_compositor() > 0) {
[14:36] <greyback> mlankhorst: 0.11 was released, I'm working off that
[14:37] <mlankhorst> hm oke
=== marcusto_ is now known as marcustomlinson
[14:59]  * alan_g disappears to reboot
[15:17] <mlankhorst> greyback: lp:~vanvugt/mir/fix-buffers_ready_for_compositor breaks it on 0.11
[15:20] <greyback> mlankhorst: ah sorry, I thought PPA 12 had released. I'm working off mir 0.11 in that ppa
[15:20] <greyback> so you need to merge all the qtmir branches listed there too, in order for anything to compile
[15:21] <mlankhorst> which was sort of what I did..
[15:21] <greyback> fix-buffers_ready_for_compositor does not go anywhere near the input code
[15:21] <mlankhorst> except the other way around, grab your branch and stuff it on top of the qtmir there
[15:22] <greyback> which should work
[15:28] <greyback> mlankhorst: running your client with MIR_CLIENT_INPUT_RECEIVER_REPORT=log will at least show if you are getting mouse events or not
[15:28] <greyback> http://unity.ubuntu.com/mir/component_reports.html out of date
[15:29] <mlankhorst> oke
[15:29] <mlankhorst> odd, don't see anything from that
[15:39] <mlankhorst> do you need debug enabled or something?
[15:50] <mlankhorst> greyback: can you try yourself with my xmir package? see if you get touch or mouse events..
[15:52] <greyback> mlankhorst: I can. Where is your xmir package? And what x app should I run?
[15:53] <mlankhorst> xev is fine
[15:53] <mlankhorst> ppa:mlankhorst/ppa, I was only getting events when holding mouse buttons in my xev window
[16:05] <kgunn_> alf_: since duflu is out of sync, would you mind keeping an eye out for assisting greyback in debugging ?
[16:05] <kgunn_> alf_: long story short...seems there's a bug, but can't repro with demo server
[16:05] <kgunn_> only happens with xmir
[16:06] <alf_> kgunn_: sure
[16:07] <alf_> greyback: ^^ let me know if you need something
[16:07] <greyback> alf_: will do, am trying to repro currently
[16:14] <greyback> mlankhorst: here's a sample of hte output I'm getting from xev: http://pastebin.ubuntu.com/10144336/
[16:15] <greyback> mlankhorst: the first chunk is pure mouse motion
[16:15] <greyback> the second chunk is me interacting with the touchscreen
[16:15] <greyback> I'm unsure how to interpret those MotionNotify events
[16:15] <greyback> what should a touch event look like to X?
[16:32] <mlankhorst> greyback: do you only get events when the button's down?
[16:33] <greyback> mlankhorst: no
[16:33] <greyback> all motion events are being reported
[16:42] <greyback> mlankhorst: there's something going weird with branches though. Trying to merge fix-buffers_ready_for_compositor into port-to-event-2.0 does nothing for me, and the build fails for that reason
[16:54] <greyback> mlankhorst: try this branch, it works for me with mir 0.11: lp:~gerboland/qtmir/port-to-event-2.0-with-mir0.11
[17:29] <racarr> Morning, lemme know if this xmir-event/2.0-qtmir thing I see in backscroll needs assistance :)
[17:29] <mlankhorst> greyback: weird..
[17:57] <racarr> confirmed that OSK bug is gone from silo
=== alan_g is now known as alan_g|EOD
[18:27] <greyback> yays