Op 21/01/2016 om 16:55 schreef Giuseppe D'Angelo:
On Thu, Jan 21, 2016 at 4:43 PM, André Somers wrote:
I was wondering: how do you know when to drop the cached data again?
When the corresponding delegate gets evicted by ListView at the end of
the removal animation.
Of course. Good point.
A
On Thu, Jan 21, 2016 at 4:43 PM, André Somers wrote:
> I was wondering: how do you know when to drop the cached data again?
When the corresponding delegate gets evicted by ListView at the end of
the removal animation.
Cheers,
--
Giuseppe D'Angelo
___
Op 21/01/2016 om 16:13 schreef Stephen Kelly:
On 21/01/16 14:56, Stephen Kelly wrote:
* Something else
As Andre wrote, 'something else' could be 'populate a "memory
structure" for all roles for the specific rows being removed in
response to rowsAboutToBeRemoved'.
I would not use all ro
On 21/01/16 14:56, Stephen Kelly wrote:
* Something else
As Andre wrote, 'something else' could be 'populate a "memory structure"
for all roles for the specific rows being removed in response to
rowsAboutToBeRemoved'.
--
Ableton AG, Schoenhauser Allee 6-7, 10119 Berlin, Germany
Management
On 21/01/16 08:12, André Somers wrote:
Actually, I think it would not need to be quite as bad.
For starters, you really only need to cache the actual items being
removed. At the moment the model emits the AboutToBeRemoved signal,
the data should still be there in any well-behaved model, righ
On 21/01/16 00:45, Andrew den Exter wrote:
On Thu, Jan 21, 2016 at 2:11 AM, Stephen Kelly
mailto:stephen.ke...@ableton.com>> wrote:
And there are the obvious runtime costs to building and
maintaining a cache that is of little or no use to most people
most of the time, which is
Op 21/01/2016 om 00:45 schreef Andrew den Exter:
On Thu, Jan 21, 2016 at 2:11 AM, Stephen Kelly
mailto:stephen.ke...@ableton.com>> wrote:
And there are the obvious runtime costs to building and
maintaining a cache that is of little or no use to most people
most of the time, w
On Thu, Jan 21, 2016 at 2:11 AM, Stephen Kelly
wrote:
>
> And there are the obvious runtime costs to building and maintaining a
> cache that is of little or no use to most people most of the time, which is
> I think a strong argument for it being an off by default feature if
> implemented.
>
>
>
On 20/01/16 01:23, Andrew den Exter wrote:
On Wed, Jan 20, 2016 at 2:13 AM, Stephen Kelly
mailto:stephen.ke...@ableton.com>> wrote:
The solution could be to cache data retrieved from the model.
That's a more complex solution than you might think. It's a pretty
popular pattern to popula
On Wed, Jan 20, 2016 at 2:13 AM, Stephen Kelly
wrote:
>
>
> https://bugreports.qt.io/browse/QTBUG-50542
>
> The remove animation happens as a result of the
> QAbstractItemModel::rowsRemoved signal, so there is a 'tension' between the
> requirements:
>
>1. An attempt in the delegate to access
On 19/01/16 14:17, Stephen Kelly wrote:
Hi,
I have uploaded a testcase to
https://github.com/ske-ableton/public_sscce/tree/master/delegate_data
which demonstrates a problem that can occur with ListView delegates
that can be animated away on removal.
I got feedback that what is happening
Hi,
I have uploaded a testcase to
https://github.com/ske-ableton/public_sscce/tree/master/delegate_data
which demonstrates a problem that can occur with ListView delegates that
can be animated away on removal.
This seems to me to be a design bug in the QML ListView. It seems to be
a simpl
12 matches
Mail list logo
