[00:16] Maybe they're getting the patch? It's not particularly invasive. [00:17] Alternatively: maybe they're not supporting EGL on mirclient? The only components which need mirclient are the various lomiri infrastructures, and they're going to be reasonably happy with a software renderer. [02:49] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF opened [pull request #2747](https://github.com/MirServer/mir/pull/2747): cmake: Fix ptest target... (full message at ) [03:00] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF edited [pull request #2744](https://github.com/MirServer/mir/pull/2744): Add core mmap-backed SHM handling [04:13] -GitHub[m]:#mir-server- **[MirServer/mir]** RAOF assigned to [pull request #2747](https://github.com/MirServer/mir/pull/2747): cmake: Fix ptest target [08:13] Good weekend o/ [08:19] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq opened [issue #2748](https://github.com/MirServer/mir/issues/2748): wlcs.Anchor/LayerSurfaceLayoutTest.is_positioned_to_accommodate_other_surfaces_exclusive_zone unstable... (full message at ) [08:20] Good morn' [09:06] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from AlanGriffiths for [pull request #2744](https://github.com/MirServer/mir/pull/2744): Add core mmap-backed SHM handling [09:49] Saviq, if you want to fixup #2747 we can land it and the follow-on [09:49] Sure, I can [09:50] I'll poke at #2748 [15:19] -GitHub[m]:#mir-server- **[MirServer/mir]** AlanGriffiths opened [pull request #2749](https://github.com/MirServer/mir/pull/2749): Fix race... (full message at ) [15:33] -GitHub[m]:#mir-server- **[MirServer/mir]** Saviq requested a review from wmww for [pull request #2749](https://github.com/MirServer/mir/pull/2749): Fix race [15:49] -GitHub[m]:#mir-server- **[MirServer/wlcs]** AlanGriffiths drafted [pull request #257](https://github.com/MirServer/wlcs/pull/257): test [15:50] -GitHub[m]:#mir-server- **[MirServer/wlcs]** AlanGriffiths edited [pull request #257](https://github.com/MirServer/wlcs/pull/257): test [17:09] Good night o/ [17:12] Does anyone know where touch scrolling is implemented? I'm working on the touch drag code right now and it prioritizes scrolling over starting a drag event. [17:13] In the client toolkit? [17:18] alan_g[m]: Thanks! Poking around right now. [20:46] There's no guarantee that clients implement touch drag and drop [21:06] "There's no guarantee that..." <- Huh, sure enough I can't drag on Weston with touch in either Firefox or Chrome. Reading over the specification for `wl_data_device`, it *never mentions* touch. I wonder if any clients have it implemented 🤔 [21:06] > <@wmww:matrix.org> There's no guarantee that clients implement touch drag and drop [21:06] * Huh, sure enough I can't drag on Weston with touch in either Firefox or Chrome. Reading over the specification for `wl_data_device`, it _never mentions_ touch with regard to drag-and-drop. I wonder if any clients have it implemented 🤔 [21:07] grayson-g[m]: In fact, `wl_data_device::enter` explicitly describes its x and y arguments as "the position of the pointer." huh [21:24] I feel like this means I should remove all touch-related logic from drag-and-drop. Any differing opinions? [22:18] "I feel like this means I..." <- Oh, wow. GTK's touch support is surprisingly poor. [22:18] RAOF: That's a +1 on removing touch-related logic from drag&drop. [23:29] -GitHub[m]:#mir-server- **[MirServer/mir]** bors[bot] merged [pull request #2743](https://github.com/MirServer/mir/pull/2743): Drop server/graphics/gl_extensions_base.cpp; it's dead code