On 2016-02-11, Thiago Macieira wrote:
>> There are several remaining issues in the report. So I have some questions:
>>
>> - Is class QPlatformScreen private and all related changes should be removed
>> from the report?
>> (http://abi-laboratory.pro/tracker/compat_report/qt/5.5.1/5.6.0-beta/8f965
Edward,
I strongly agree with your analysis. Any generalized touch (marker, finger,
pen) has a general elliptic shape defined by a rectangle, when a device
does not support that info, touches are just degenerate squares 0 by 0 and
zero area. But richer devices might provide blob rect and blob angl
On Thu, Feb 11, 2016 at 6:31 AM, Rutledge Shawn <
shawn.rutle...@theqtcompany.com> wrote:
>
> > On 11 Feb 2016, at 11:35, Александр Волков
> wrote:
> > Angle is not enough, because for compatibility with older apps
> TouchPoint::rect() should be as close as possible to the rotated rect.
> > See h
>
> I’m interested. But I will warn you that my attempts to make MouseArea
> and Flickable handle touch events directly have run into issues with the
> complexity of handling two completely independent event types with
> similar-but-different code, backwards compatibility, getting reviews on the
>
>
>
>> There is QTouchEvent::device(). Isn't it enough?
>
>
> - Area & rotation. There is TouchPoint::area() and ::pressure() but
>> currently there is no support for ::angle(). Angle can be zero when not
>> supported.
>>
> Angle is not enough, because for compatibility with older apps
> TouchPoi
Another advantage for end users is that they are guaranteed to get the latest
platform features supported by that version of Qt if their OS version also
supports them.
For example, if Qt is built with the 10.11 SDK and therefore provides a fast
WKWebView implementation, users running on 10.11 w
On quinta-feira, 11 de fevereiro de 2016 13:26:50 PST Konstantin Ritt wrote:
> BTW, *_wcsicmp* compares strings by simply converting them to their
> lowercase forms.
> So what you suggest? Changing Qt::CaseInsensitive string comparison to not
> use casefolding and introduce more option(s) for case-
On quinta-feira, 11 de fevereiro de 2016 16:46:52 PST Ponomarenko Andrey
wrote:
> I've removed most of the false positives mentioned in the review from the
> report: http://abi-laboratory.pro/tracker/timeline/qt/
Thanks Andrey!
>
> There are several remaining issues in the report. So I have som
Very much a digression but ...
> TUIO models the touchpoint as a rotated ellipse though, right? [snip
> URL] And I think that’s nice, for finger touchpoints at least
> (although markers could be any shape). It can be assumed to be the
> ellipse inscribed in a rect
Traditional graphics always th
05.02.2016, 19:58, "Thiago Macieira":
> On sexta-feira, 5 de fevereiro de 2016 16:34:19 PST Ponomarenko Andrey wrote:
>> Hello,
>>
>> I've started to maintain API/ABI changes report for the Qt library here:
>> http://abi-laboratory.pro/tracker/timeline/qt/
>
> Hello Andrey
>
> Thank you for the
On 10/02/16 22:07, Thiago Macieira wrote:
If we're going to upgrade our Xcode in all our builds, I would advise we
also make it mandatory for everyone else too. Check during configure
against the minimum SDK version, that being the *current* at the time of
release.
Yes, absolutely.
To be clea
> On 11 Feb 2016, at 11:35, Александр Волков wrote:
> Angle is not enough, because for compatibility with older apps
> TouchPoint::rect() should be as close as possible to the rotated rect.
> See https://codereview.qt-project.org/#/c/114238/
> In other words it should be a projection of the rota
> On 11 Feb 2016, at 02:13, Ariel Molina wrote:
>
> Hi,
>
> Research is strong on natural user interfaces, and now market is stronger
> than ever and growing. I was working on the TUIO QPA and found a couple of
> bugs, which I already pushed patches [1] [2] which I hope make it to 5.6.x.
>
Hi, Ariel.
11.02.2016 04:13, Ariel Molina пишет:
- Multiple touch devs/layers and Person tagged touches. Can be easily
added by extending QWindowSystemInterface::TouchPoint with a device
identification, like device(). This will also work for TUIO.
There is QTouchEvent::device(). Isn't it enoug
2016-02-11 3:47 GMT+04:00 Thiago Macieira :
> On quinta-feira, 11 de fevereiro de 2016 03:00:02 PST Konstantin Ritt
> wrote:
> > > CaseSensitive => no case folding, no
> > > normalisation
> > > CaseSensitiveNormalized => no case folding, but normalised
> >
> On Feb 10, 2016, at 6:36 PM, Petroules Jake
> wrote:
>
>
>> On Feb 10, 2016, at 8:11 AM, Tor Arne Vestbø
>> wrote:
>>
>> On 10/02/16 17:06, Thiago Macieira wrote:
>>> On quarta-feira, 10 de fevereiro de 2016 12:00:00 PST Tor Arne Vestbø wrote:
Does anyone see any issues with this goi
16 matches
Mail list logo
