I have filed https://javafx-jira.kenai.com/browse/RT-39917 for this in Jira.
On Wed, Jan 28, 2015 at 5:57 PM, Robert Krüger krue...@lesspain.de wrote:
On Wed, Jan 28, 2015 at 5:55 PM, Robert Krüger krue...@lesspain.de
wrote:
OK, I investigated some more.
What is weird is that the same
Hi,
On Wed, Jan 28, 2015 at 1:59 PM, Werner Lehmann
lehm...@media-interactive.de wrote:
Robert,
I think Tomas is right, load your thumbnails on demand when updateItem is
called for an item with missing thumbnail. You say that the cell of a
visible item gets reused for another item. If that
Doesn't help. The patterns of this property being changed are just as
unusable for my purposes as with the other approaches (e.g. I can clearly
see that item is set to a different value for a cell that is still visible,
so this would falsely cancel the loading of that cell's image). And since
none
Robert,
I think Tomas is right, load your thumbnails on demand when updateItem
is called for an item with missing thumbnail. You say that the cell of a
visible item gets reused for another item. If that is the case I guess
that the item is moved to another cell. Wouldn't it be possible to
forgot again to reply to all. If anyone ever considers changing the default
settings of the list server, +1 from me.
-- Forwarded message --
From: Robert Krüger krue...@lesspain.de
Date: Wed, Jan 28, 2015 at 3:47 PM
Subject: Re: TableView API, no lazy retrieval of visible cell
On Wed, Jan 28, 2015 at 5:55 PM, Robert Krüger krue...@lesspain.de wrote:
OK, I investigated some more.
What is weird is that the same table cell instance (I checked the Object
hashcode) is set to different model values while it is still visible, i.e.
I get sequences like this in the log,
OK, hang on. I may have found a mistake and what I described may not
actually have been happening.
On Wed, Jan 28, 2015 at 3:13 PM, Robert Krüger krue...@lesspain.de wrote:
Hi,
On Wed, Jan 28, 2015 at 1:59 PM, Werner Lehmann
lehm...@media-interactive.de wrote:
Robert,
I think Tomas is
Yes, and I think there was a mistake in my code. I have it almost working
and have to analyse now, why it does not work for all cells, which may
again be my mistake. I will investigate and post an update and if I don't
find it, I will build a simple test program to illustrate this.
On Wed, Jan
Hi Robert,
instead of listening to visibleProperty(), listen to sceneProperty()
and cancel loading when scene becomes null.
Tomas
On Tue, Jan 27, 2015 at 1:16 PM, Robert Krüger krue...@lesspain.de wrote:
Hi,
either I don't see the forest for the trees or something is missing in the
Hi Tomas,
When I do that, the property is never set to null. If I use it for
triggering the loading (when it is set to a non-null value) it is set for a
lot more rows than those actually visible. In my test with a model
containing 200 items of which the first 4 were visible, it was set to
If the cells don't ever get removed from the scene, then I guess your
best bet is to start and cancel loading when the item changes, i.e.
listening to itemProperty(). This is similar to your original
updateItem() approach, but also don't forget to cancel loading of the
old item: cancel loading of
11 matches
Mail list logo
