Fixed #1272

[AlexandruPopovici]

…anges were set. Implemented a draw range flattener for the PointBatch which avoids redundant draw calls, which in some cases could get into the tens of thousands killing performance entirely. Fixed an issue where gradient ramp index was not neing set correctly when it was 0

Description & motivation

This #1272 was raised, describing two issues. One with performance when applying filters on a specific stream and another one where successive gradient filters were not being applied correctly. The reported bugs were a good catch since they can potentially affect any stream

Changes:

• Fixed an issue with PointBatch auto fill draw ranges, where invalid ranges were set, and any points in that batch would not be rendered
• Implemented a draw range flatten-er for the PointBatch which avoids redundant draw calls, which in some cases could get into the tens of thousands killing performance entirely. This was the case in Viewer Filter's Performance and Bug #1272 where several tens of thousand of points each got their own draw group even though all of them had the same material index.
• Fixed an issue where gradient ramp index was not being set correctly when it was 0

To-do before merge:

Screenshots:

Validation of changes:

Checklist:

• My pull request follows the guidelines in the Contributing guide?
• My pull request does not duplicate any other open Pull Requests for the same update/change?
• My commits are related to the pull request and do not amend unrelated code or documentation.
• My code follows a similar style to existing code.
• I have added appropriate tests.
• I have updated or added relevant documentation.

References