Posted 11 August 2021, 7:10 am EST
Hi Shiva,
I’ve updated the sample as per your requirement.
- The lightning effect was caused because the collectionView was getting refreshed after every disabled checkbox gets unchecked, so to resolve the issue instead of setting the row isSelected property you may set the checkbox’s checked property to false. You also need to change the isSelected property state for the disabled rows by calling unCheckDisabledRow method in the itemChecked event of selector Class and pageChanged event of collectionView to do the same on the next page.
Please refer to the updated sample:
https://stackblitz.com/edit/angular-zs8gny
- I am afraid this will be expected behavior. When the select all checkbox is checked, some of the rows are unchecked (as per the requirement), the checkbox goes into an indeterminate state. But after the indeterminate state, the checkbox will always go into the checked state (browser’s behavior) and will check all the rows again but due to some rows not being selected it will go back into an indeterminate state. So I would suggest you either check all the rows or implement a custom selection checkbox without using the Selectors.
Regarding platinum license, you can post your queries on the my support portal in your account:
https://www.grapecity.com/my-account/my-support
and we will try to reply within 24 hours (except on weekends). But sometimes, due to the complexity of the query, it may take use more than 24 hours to provide a response. In that case we will update you accordingly.
~regards