yes, that's what appear's to be happening.
On Sat, Jan 24, 2015 at 9:33 PM, Scott Palmer swpal...@gmail.com wrote:
You are probably only seeing the event when the TableView's internal
ScrollPane doesn't consume it.
Scott
On Jan 24, 2015, at 11:50 AM, Robert Krüger krue...@lesspain.de
You are probably only seeing the event when the TableView's internal ScrollPane
doesn't consume it.
Scott
On Jan 24, 2015, at 11:50 AM, Robert Krüger krue...@lesspain.de wrote:
Hi,
yes, I just now realized that setOnScroll is Node API and not TableView so
I obviously sent my Mail too
[sorry sent the other mail too early]
Hi,
I don't really see why you need to know about this all view classes are
virtual so a TableCell, ListCell is only requested when shown - and then
reused.
IIRC this virtuallity is row based only but the otn request also only
talks about rows.
One more
Hi,
I am a bit surprised by the behaviour of the onScroll event handling of
TableView. I just printed the events I received there to standard out and
although the table does not display any scrollbars because it is large
enough to fit all content into it, I receive events as if it were scrolling
I don't really see why you need to know about this all view classes are virtual
so a TableCell, ListCell is only requested when shown - and then reused - IIRC
this virtuallity is row based only but the otn request also only talks about
rows.
Tom
Von meinem iPhone gesendet
Am 24.01.2015 um
Hi,
yes, I just now realized that setOnScroll is Node API and not TableView so
I obviously sent my Mail too early.
Sorry about the noise.
Another observation, though: The onscroll-eventhandler is not called when
the tableview actually does scroll. It does fire again, when I reach one
end of the
