I started getting this error (actually not an error but the listview display gets erratic and I get these warnings in the log window):
repeated every time a new item gets added to the listview. Actually, I get both messages two or three times for each item added to the listview.
It does not start immediately, it runs for a few seconds (exactly 289 messages).
I am using B4J v10.30 and jdk 19
I have created the minimum program necessary to show the problem. It's just a listview and a timer
I does the same in debug and release mode.
I have not seen anything recent about this but just in case, I updated everything that I could on this Dell Precision 3551 including the display drivers just yesterday to make sure that was not the issue.
It runs Windows 10 Pro and has an NVidia Quadro graphic chip.
That machine has 64GB of RAM, so that's probably not the issue...
If I remove the ScrollTo statement, there is no problem.
I use the same construct on other machines and so far I have not seen that problem. This machine used to run this code with no complaints. Not sure what I did to get this started...
TIA
Edit: I changed the timer from 20mS to 200mS and it started doing it after exactly 289 messages regardless of the timer setting, so it does not seem like time is a factor.
B4X:
Aug 13, 2025 4:00:13 PM javafx.scene.control.skin.VirtualFlow addTrailingCells
INFO: index exceeds maxCellCount. Check size calculations for class anywheresoftware.b4j.objects.ListViewWrapper$MyCallBack$1
repeated every time a new item gets added to the listview. Actually, I get both messages two or three times for each item added to the listview.
It does not start immediately, it runs for a few seconds (exactly 289 messages).
I am using B4J v10.30 and jdk 19
I have created the minimum program necessary to show the problem. It's just a listview and a timer
I does the same in debug and release mode.
I have not seen anything recent about this but just in case, I updated everything that I could on this Dell Precision 3551 including the display drivers just yesterday to make sure that was not the issue.
It runs Windows 10 Pro and has an NVidia Quadro graphic chip.
That machine has 64GB of RAM, so that's probably not the issue...
If I remove the ScrollTo statement, there is no problem.
I use the same construct on other machines and so far I have not seen that problem. This machine used to run this code with no complaints. Not sure what I did to get this started...
TIA
Edit: I changed the timer from 20mS to 200mS and it started doing it after exactly 289 messages regardless of the timer setting, so it does not seem like time is a factor.
Attachments
Last edited: