Re: [Interest] TapHandler tapped coordinates not accessible

2019-05-06 Thread Tomasz Olszak
I would like to move to new input handling from old pinch area etc. Shawn that was what I was looking for. Any idea why it is not documented? pon., 6 maj 2019 o 21:56 Shawn Rutledge napisał(a): > > > On 6 May 2019, at 16:30, Tomasz Olszak wrote: > > > > Hi, > > > > I use Qt 5.12.3 and I'm

Re: [Interest] TapHandler tapped coordinates not accessible

2019-05-06 Thread Shawn Rutledge
> On 6 May 2019, at 16:30, Tomasz Olszak wrote: > > Hi, > > I use Qt 5.12.3 and I'm trying to use TapHandler. For some reason though in > onTapped handler point is already reset. > I see that point is valid when reading it from onPressedChanged. Is it a bug? > Seems like docs miss explicit

Re: [Interest] TapHandler tapped coordinates not accessible

2019-05-06 Thread Jason H
Taps are for taps, that a thing was tapped. Not where. Generally if you want points, you get the press/down/move event and save the coordinate there, then on the tap event, check what was saved. Sometimes . Maybe PointHandler is what you want? I often would like the x,y on an onClicked() handler,

[Interest] TapHandler tapped coordinates not accessible

2019-05-06 Thread Tomasz Olszak
Hi, I use Qt 5.12.3 and I'm trying to use TapHandler. For some reason though in onTapped handler point is already reset. I see that point is valid when reading it from onPressedChanged. Is it a bug? Seems like docs miss explicit example of reading point coordinate. This is snippet I use to test.

Re: [Interest] Interest Digest, Vol 92, Issue 5

2019-05-06 Thread Giuseppe D'Angelo via Interest
Il 05/05/19 15:07, Roland Hughes ha scritto: On 5/5/19 5:00 AM, interest-requ...@qt-project.org wrote: It makes for a lot of documentation in the embedded system world where every static_cast<>() has to be documented in the code and justified in a formal code review which produces even more