Re: Batching text input protocol changes

2020-02-18 Thread Dorota Czaplejewicz
On Tue, 18 Feb 2020 16:20:08 +0100 Jonas Ådahl wrote: > On Tue, Feb 18, 2020 at 04:14:50PM +0100, Dorota Czaplejewicz wrote: > > On Tue, 18 Feb 2020 10:12:11 +0200 > > Pekka Paalanen wrote: > > > > > On Mon, 17 Feb 2020 19:58:43 +0100 > > > Dorota Czaplejewicz wrote: > > > > > > > Hi all,

Re: Batching text input protocol changes

2020-02-18 Thread Jonas Ådahl
On Tue, Feb 18, 2020 at 04:14:50PM +0100, Dorota Czaplejewicz wrote: > On Tue, 18 Feb 2020 10:12:11 +0200 > Pekka Paalanen wrote: > > > On Mon, 17 Feb 2020 19:58:43 +0100 > > Dorota Czaplejewicz wrote: > > > > > Hi all, > > > > > > over the past month, the zwp_text_input_v3 protocol has moved

Re: Batching text input protocol changes

2020-02-18 Thread Dorota Czaplejewicz
On Tue, 18 Feb 2020 10:12:11 +0200 Pekka Paalanen wrote: > On Mon, 17 Feb 2020 19:58:43 +0100 > Dorota Czaplejewicz wrote: > > > Hi all, > > > > over the past month, the zwp_text_input_v3 protocol has moved to real > > devices and had seen unprecedented usage. Together with that, it also > > g

Re: Batching text input protocol changes

2020-02-18 Thread Johan Helsing
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: Batching text input protocol changes

2020-02-18 Thread Jonas Ådahl
On Tue, Feb 18, 2020 at 10:12:11AM +0200, Pekka Paalanen wrote: > On Mon, 17 Feb 2020 19:58:43 +0100 > Dorota Czaplejewicz wrote: > > > Hi all, > > > > over the past month, the zwp_text_input_v3 protocol has moved to real > > devices and had seen unprecedented usage. Together with that, it also

Re: Batching text input protocol changes

2020-02-18 Thread Pekka Paalanen
On Mon, 17 Feb 2020 19:58:43 +0100 Dorota Czaplejewicz wrote: > Hi all, > > over the past month, the zwp_text_input_v3 protocol has moved to real > devices and had seen unprecedented usage. Together with that, it also > got a reality check, from which it didn't come unscathed. There are > some i