On 10/15/2016 6:59 PM, Roland Hughes wrote:
When you work off nothing but stories you are hacking on the fly...
Ok, since I've responded to this before (perhaps this should be a different
thread?), I'll jump in there again and clarify where /I'm/ coming from...
First, let me say I embrace Ag
On 2016-10-15 20:59, Roland Hughes wrote:
> On 09/28/2016 12:25 PM, interest-requ...@qt-project.org wrote:
>
> Don't you have unit tests?
>
> Yes. But which is better, to be forced to use an inherently error-prone
> language (JavaScript) and rely on unit tests to clean up the mess, or to
> use a
> -Original Message-
> From: J-P Nurmi
> Sent: Sunday, 16 October 2016 4:06 PM
> To: Mitch Curtis ; Qt Project
> Subject: Re: Mouse event propagation in Qt Quick
>
> Hey Mitch,
Hey!
>
> > - In example #2, why is Flickable happy to steal events that it doesn't do
> anything with? Should
Hey Mitch,
> - In example #2, why is Flickable happy to steal events that it doesn't do
> anything with? Shouldn't it see that it wasn't a "flick" and ignore the
> event, so that it goes to the next highest item in the stacking order (the
> mouse area)?
An interactive Flickable always accepts
Hi.
In the following example (#1), I want both the MouseArea to be clickable and
the scroll bars to be draggable:
import QtQuick 2.7
import QtQuick.Window 2.2
import QtQuick.Controls 2.0
Window {
visible: true
width: 640
height: 480
title: qsT
