New point of contact for Qt

y the best point of contact from now on. I will still be reachable on mail (johanhels...@gmail.com) and freenode (johanhelsing), and try to answer if there are questions about qtwayland, but you will probably have to ping me specifically to get my attention. Br, Joh

Re: Batching text input protocol changes

Same for us in Qt. When we implement a new version of the protocol, we copy it manually from wayland-protocols into qtwayland/src/3rdparty/protocol, that way we can support new versions regardless of which old-as-dirt wayland-protocols version is shipped with the device. I think that if we'd ha

Re: wayland-protocols scope and governance

Hi, Thanks for asking, a membership for Qt would would be much appreciated! I'm probably the best point of contact. I've read through the document (v5) and it makes sense to me. Acked-by: Johan Helsing Qt has interest in the project both as a compositor toolkit and as a client to

Re: Possible Wayland Extension to publish Mouse Pointer Size

Hi Simon, Sorry for not participating more activively in the discussion. Your summary makes sense to me. > Some people (from KDE, GLFW if I recall correctly) said > there's some overhead in loading cursors on the client-side (a few megabytes, > I/O when loading images) and that could be saved. H

Re: [PATCH RFC wayland-protocols] unstable: add xcursor-configuration

Hi Simon, Thanks for working on this! :) Is the intention to implement the client side inside libwayland-cursor? No changes needed for toolkits except calling some new API when initializing libwayland-cursor? I guess it's also possible to implement it on the toolkit level using the old libwaylan