>
> No. ListView is designed to support many interaction methods, not a
> specific interaction method with others being "custom things". Aside
> from the case where you want more than click-to-select in your
> MouseArea (which is probably the most common case, and would require
> overriding any de
On Mon, Jan 28, 2013 at 11:56 PM, Rainer Keller wrote:
> Hi,
>
>> Having
>> a MouseArea "by default" would most likely lead to it being disabled
>> in the majority of cases, on all platforms except desktop.
> I agree. But this doesn't this affect mobile touch devices too?
Some mobile UIs have tap
Hi,
> Having
> a MouseArea "by default" would most likely lead to it being disabled
> in the majority of cases, on all platforms except desktop.
I agree. But this doesn't this affect mobile touch devices too?
> This is a different problem (probably easiest solved with a link to
> the examples, li
On Mon, Jan 28, 2013 at 12:36 AM, Rainer Keller wrote:
> Hi,
>
>
>
> I tried to use a QML ListView and wondered why it does not react to mouse
> clicks. After looking into the examples I found out that you need to add a
> MouseArea in the delegate. Without this code the ListView is unusable
> beca
On Mon, Jan 28, 2013 at 8:36 AM, Rainer Keller wrote:
> **
>
> Hi,
>
>
>
> I tried to use a QML ListView and wondered why it does not react to mouse
> clicks. After looking into the examples I found out that you need to add a
> MouseArea in the delegate. Without this code the ListView is unusable
Hi,
I tried to use a QML ListView and wondered why it does not react to mouse
clicks. After looking into the examples I found out that you need to add a
MouseArea in the delegate. Without this code the ListView is unusable because
the user can not select anything using the mouse.
Shouldn't the
