> On 28 Sep 2017, at 16:54, Shawn Rutledge wrote:
>
>
>> On 28 Sep 2017, at 13:36, J-P Nurmi wrote:
>>
>>> On 28 Sep 2017, at 13:07, Tor Arne Vestbø wrote:
>>>
>>> On 28/09/2017 13:05, Tor Arne Vestbø wrote:
If we can't have a generic GestureRecognizer type with dynamic recognizer
> On 28 Sep 2017, at 13:36, J-P Nurmi wrote:
>
>> On 28 Sep 2017, at 13:07, Tor Arne Vestbø wrote:
>>
>> On 28/09/2017 13:05, Tor Arne Vestbø wrote:
>>> If we can't have a generic GestureRecognizer type with dynamic recognizer
>>> behavior based on which handler callback is bound, then it sho
> Sent: Thursday, September 28, 2017 at 8:20 AM
> From: "André Somers"
> To: development@qt-project.org
> Subject: Re: [Development] Pointer Handlers will be Tech Preview in 5.10
>
>
>
> Op 28/09/2017 om 13:42 schreef Tor Arne Vestbø:
> > On 28/09/2
Op 28/09/2017 om 13:42 schreef Tor Arne Vestbø:
> On 28/09/2017 13:36, J-P Nurmi wrote:
>> I would prefer attached properties and signals. Similarly to
>> Keys.onPressed. Attaching onTapped from the outside of a component
>> would be similar to overriding an event handler in C++. There would
>> b
On 28/09/2017 13:36, J-P Nurmi wrote:
I would prefer attached properties and signals. Similarly to
Keys.onPressed. Attaching onTapped from the outside of a component
would be similar to overriding an event handler in C++. There would
be a single attached object instance with multiple signal handl
> On 28 Sep 2017, at 13:07, Tor Arne Vestbø wrote:
>
> On 28/09/2017 13:05, Tor Arne Vestbø wrote:
>> If we can't have a generic GestureRecognizer type with dynamic recognizer
>> behavior based on which handler callback is bound, then it should be
>> TapGestureRecognizer, DragGestureRecognizer,
On 28/09/2017 13:05, Tor Arne Vestbø wrote:
If we can't have a generic GestureRecognizer type with dynamic
recognizer behavior based on which handler callback is bound, then it
should be TapGestureRecognizer, DragGestureRecognizer, etc.
Or if we want to follow the existing naming of MouseArea
On 27/09/2017 21:18, J-P Nurmi wrote:
On 27 Sep 2017, at 21:08, Jean-Michaël Celerier
wrote:
Why not just Drag, Tap, Pinch ? (for Drag it'd have to be in a
different namespace than the actual QtQuick.Drag though)
Best,
+1 for such Qt Quick style short and concise naming. :) This proposal
wa
> On 27 Sep 2017, at 21:08, Jean-Michaël Celerier
> wrote:
>
> Why not just Drag, Tap, Pinch ? (for Drag it'd have to be in a different
> namespace than the actual QtQuick.Drag though)
>
> Best,
+1 for such Qt Quick style short and concise naming. :) This proposal was
previously shot down b
Why not just Drag, Tap, Pinch ? (for Drag it'd have to be in a different
namespace than the actual QtQuick.Drag though)
Best,
---
Jean-Michaël Celerier
http://www.jcelerier.name
On Wed, Sep 27, 2017 at 7:56 PM, J-P Nurmi wrote:
> On 27 Sep 2017, at 17:35, Shawn Rutledge wrote:
>
>
> On 27
On 27 Sep 2017, at 17:35, Shawn Rutledge
mailto:shawn.rutle...@qt.io>> wrote:
On 27 Sep 2017, at 16:52, J-P Nurmi mailto:jpnu...@qt.io>> wrote:
On 9 Aug 2017, at 14:10, Shawn Rutledge
mailto:shawn.rutle...@qt.io>> wrote:
[…] So far we only have
TapHandler - […]
DragHandler - […]
PinchHandler
> On 27 Sep 2017, at 16:52, J-P Nurmi wrote:
>
>> On 9 Aug 2017, at 14:10, Shawn Rutledge wrote:
>>
>> […] So far we only have
>>
>> TapHandler - […]
>> DragHandler - […]
>> PinchHandler - […]
>>
>
>
> Hi Shawn,
>
> Why are these types called “handlers”? Because we use term “event handler
> On 9 Aug 2017, at 14:10, Shawn Rutledge wrote:
>
> […] So far we only have
>
> TapHandler - […]
> DragHandler - […]
> PinchHandler - […]
>
Hi Shawn,
Why are these types called “handlers”? Because we use term “event handler” for
those methods that you override in C++? IMHO “handler” type n
We just finally got the wip/pointerhandler branch merged to dev branch (yes
it’s a couple of days past the feature freeze, but has been in the works for
years, and we really planned to get it in 5.10).
A PointerHandler is a QObject which can be declared as a child of an Item in Qt
Quick, which
14 matches
Mail list logo
