| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| === chihchun is now known as chihchun_afk | ||
| === chihchun_afk is now known as chihchun | ||
| === chihchun is now known as chihchun_afk | ||
| mlankhorst | racarr_: how are multiple touchpoints supported by mir currently? | 10:55 |
|---|---|---|
| anpok | mlankhorst: the MirMotionEvent inside MirEvent stores an array of MirMotionPointer, this part is currently redone with the MirEvent-2.0 proposal.. | 11:14 |
| mlankhorst | anpok: yeah but I mean there can be multiple fingers then? | 11:15 |
| anpok | yes | 11:15 |
| mlankhorst | ok | 11:15 |
| mlankhorst | what about touchpads? | 11:28 |
| === dandrader is now known as dandrader|afk | ||
| alan_g | greyback_: have your concerns been addressed here? https://code.launchpad.net/~mir-team/mir/allow-lock-surf-orientation/+merge/242984/comments/599192 | 12:35 |
| greyback_ | alan_g: yeah, it's good for me | 12:39 |
| alan_g | thanks | 12:40 |
| === dandrader|afk is now known as dandrader | ||
| mlankhorst | how do you get a ppa for phone? | 13:01 |
| alf__ | mzanetti: greyback_: What's the requirement for the cursor in terms of enabling it and disabling it on the phone? Do you want runtime control or will a flag to USC be enough (I guess the first)? | 13:16 |
| mzanetti | alf__: I guess in the end we want runtime control in any case | 13:17 |
| * greyback_ agrees, runtime would be ultimate goal | 13:17 | |
| mzanetti | but for a start any of those would be ok I guess... maybe Gerry has some more ideas | 13:18 |
| alf__ | greyback_: mzanetti: OK, I will start with a flag to USC to move more quickly and unblock you. We can move to something more elaborate later. | 13:21 |
| === dandrader_ is now known as dandrader | ||
| === dandrader is now known as dandrader|lunch | ||
| === chihchun_afk is now known as chihchun | ||
| === dandrader|lunch is now known as dandrader | ||
| attente_ | RAOF: is that like a full-screen transparent input-only surface? | 17:30 |
| racarr_ | mlankhorst: Each pointer_coordinate in the MirEvent array is a touchpoint and each MirEvent for a given device will report the state of ALL touchpoints, uh | 17:48 |
| racarr_ | as mentioned its being redone, to take care of issues like | 17:48 |
| racarr_ | touchpads don't really work because you cant introspect various axes and see which are relative/absolute | 17:49 |
| racarr_ | + all the touchpad emulation stuff is missing, e.g. two finger scroll, etc | 17:49 |
| === chihchun is now known as chihchun_afk | ||
| mlankhorst | racarr_: yeah the thing I need | 18:04 |
| === alan_g is now known as alan_g|EOD | ||
| mlankhorst | racarr_: will it use libinput? | 18:14 |
| racarr_ | mlankhorst: Yes. | 18:14 |
| mlankhorst | yay | 18:14 |
| racarr_ | Work is underway to use libinput/android stack per device | 18:15 |
| racarr_ | :) | 18:15 |
| RAOF | attente_: No, it's a surface that captures the mouse (and will capture most keys, too) on focus, among other things. | 20:09 |
| attente_ | RAOF: ah, cool. any idea when it will be available in mir? | 20:14 |
| RAOF | attente_: Not really, sorry. | 20:15 |
| RAOF | attente_: It's on the backlog, but not one of the current priorities. | 20:15 |
| attente_ | RAOF: ok, thanks | 20:15 |
| attente_ | RAOF: do you know if there's a way to set the z position of a surface through the client api for a multi-surface application? | 20:17 |
| RAOF | Not currently. | 20:18 |
| RAOF | I'm not sure if we'll expose that capability (as opposed to raising surfaces). | 20:18 |
| attente_ | oh ok. that's what i wanted actually, just to be able to bring a particular surface to the front | 20:19 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!