This PR addresses the issue where it was not possible to scroll to items beyond the 100th item (this problem surfaced while testing the fix for issue #61). The underlying problem was an unusual behavior of scrolling in the table view, which has been fixed in later Java FX versions. For detailed information, please refer to the JavaDoc in the JumpingScrollingPositionIssueConcealer.class.
Although this PR conceals the issue to some extent, it does not provide a definitive solution. Better approaches:
Upgrading the Java version being used.
Modifying the lazy-loading behavior of the siard-suite: Implementing pagination for large tables. With pagination, data doesn't need to be reloaded on-the-fly, and the scrolling-position bug will never occur. Pagination also improves performance and user experience.
For instance, navigating to the last entry in a DB table: with the current solution, a user needs to scroll until the last entry is loaded. The entire table is loaded in-memory, which can lead to OutOfMemoryExceptions. With pagination, only the data of the current page is loaded, and the user only needs to scroll through that page to reach the last entry.
This PR addresses the issue where it was not possible to scroll to items beyond the 100th item (this problem surfaced while testing the fix for issue #61). The underlying problem was an unusual behavior of scrolling in the table view, which has been fixed in later Java FX versions. For detailed information, please refer to the JavaDoc in the JumpingScrollingPositionIssueConcealer.class.
Although this PR conceals the issue to some extent, it does not provide a definitive solution. Better approaches: