Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

> On 26 Apr 2016, at 14:56, Simon Hausmann wrote: > > Hi, > > The way you describe the problem sounds like it is specific to tablet events > on X-Windows. In my opinion a solution to the problem applied to the 5.6 > branch of Qt > should also be limited to tablet events

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On Wed, 27 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote: On Wednesday 27 April 2016 08:50:48 Boudewijn Rempt wrote: [snip] As a Debian developer, you might also consider that you should never ever package Krita 3 for Debian with a Qt 5.6 without this fix. You'd have to carry the patch

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On Wednesday 27 April 2016 08:50:48 Boudewijn Rempt wrote: [snip] > As a Debian developer, you might also consider that you should never > ever package Krita 3 for Debian with a Qt 5.6 without this fix. You'd have > to carry the patch for Qt 5.6 or forego packaging Krita (and later on, >

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On Tue, 26 Apr 2016, Lisandro Damián Nicanor Pérez Meyer wrote: Please correct me if I'm wrong: the feature which will break API was added in 5.6.0, and we can say that most of the people out there are not using it. Ideally API/ABI should not be broken without a SONAME change. If I had some

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On terça-feira, 26 de abril de 2016 20:51:30 PDT Lisandro Damián Nicanor Pérez Meyer wrote: > Please correct me if I'm wrong: the feature which will break API was added > in 5.6.0, and we can say that most of the people out there are not using > it. No ABI breakage happened. There's a change in

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

Please correct me if I'm wrong: the feature which will break API was added in 5.6.0, and we can say that most of the people out there are not using it. Ideally API/ABI should not be broken without a SONAME change. If I had some Qt5 app using it already I would be forced to do a hack in our

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

El Tuesday 26 April 2016, Shawn Rutledge escribió: > Personally I think event compression should be a cross-platform feature if > we’re going to have it. The event-pileup problem can happen also on > Windows for example, but it seems that we never implemented event > compression on any platform

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On terça-feira, 26 de abril de 2016 10:02:46 PDT Matthew Woehlke wrote: > Since when does SC mean that code written for version Y must compile > against version X (X < Y)? Usually it's only the other way around... Or > do I not understand what would break, here? (Is the problem just that > code

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On 2016-04-26 08:08, Shawn Rutledge wrote: > If the application does not handle high-frequency events (mouse > movements and window moves/resizes) quickly enough, some events will > be dropped. Do you really mean dropped? Or do you mean merged? There is a HUGE difference... Please don't EVER

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

Hi, The way you describe the problem sounds like it is specific to tablet events on X-Windows. In my opinion a solution to the problem applied to the 5.6 branch of Qt should also be limited to tablet events on X-Windows. Wouldn't it therefore be easiest to simply not do tablet event

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

On Tue, Apr 26, 2016 at 1:08 PM, Shawn Rutledge wrote: > > > I was told to request this exception on the mailing list, because we usually > try to maintain source compatibility between releases. > > So, any objections? (Having been the one asking for bringing the matter up

Re: [Development] Exception to source compatibility: adding AA_CompressHighFrequencyEvents flag

> On 26 Apr 2016, at 14:08, Shawn Rutledge wrote: > > Personally I think event compression should be a cross-platform feature if > we’re going to have it. The event-pileup problem can happen also on Windows > for example, but it seems that we never implemented event