ParamQuery grid support forum
General Category => Bug Report => Topic started by: paulguz on February 06, 2018, 05:55:42 pm
-
Hi,
I'm evaluating ParamQueryPro 5.1 on an iPad Air running iOS 11.2.5.
When scrolling a grid with grouped columns, the scrolling can be very flickery indeed. Sometimes cells are not rendered (are blank).
You can witness this yourself by viewing your own Export Grouped Columns demo at paramquery.com/pro/demos
Regards,
Paul
-
Any thoughts? Our purchase of a Pro licence is contingent on this being fixed.
-
For performance reasons and to support unlimited number of rows and columns, in pqgrid, cells are rendered only in the viewport, which means cells are created and destroyed continuously as the view is scrolled.
In touch devices, scroll event is fired at a longer interval, resulting in skipping of rendering and painting of some of the new cells.
This skipping happens only when the view is scrolled.
When scrolling is stopped, all the cells are rendered in viewport, thus from our viewpoint this is not an issue and there is no plan to change it.
-
I'm afraid that doesn't match our experience. Cells are left blank even after scrolling.
The flickering whilst scrolling isn't a good experience, either.
Please see the below video.
https://datapa-my.sharepoint.com/:v:/p/pguz/EXXhIPTprBZIsHyuGiX-3PcBY2IvhVoKvzf_Wnldo_yYhA?e=AYc2iQ
-
Do you face this issue with grouped columns only or with all examples.
-
It seems to be only with grouped columns.
-
That's strange.
Is it the same issue in Chrome browser and/ or opening example in a new tab / window.
-
Yes and yes
It has to work in Safari, supporting the stock browser is of the utmost importance.
-
Ok, there is another example on grouped columns: https://paramquery.com/pro/demos/infinite
Is it the same issue with this one too?
-
No, it seems OK on that one.
-
Any more thoughts? As previously stated, we can't purchase a Pro licence unless this is fixed.
-
Thanks for reporting issue.
The issue of cells left blank while scrolling has been identified and fix would be available in upcoming version.
-
Thanks very much. Looking forward to trying out the new version when it comes.
-
This is fixed in v5.2.0