You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With ccmanager I have a backend refresh system that updates list items from time to time. It uses SetItem to update the item when it is changed and uses Index to get the index of the item to replace. However, when filtering is used, Index returns the index of the selected filtered item and not which index the item holds in the slice of all items.
To be backwards compatible, I'd propose a "IndexOfSelectedItem" variable to get the index of the currently selected item in the slice of all items.
Or am I missing something here?
The text was updated successfully, but these errors were encountered:
When calling the SetItems method while filtering, the current filtered list is set to null, only for the pagination to be updated with the m.updatePagination() call. This then sets the index to 0, since there are no items in the filteredItems.
Commenting line 341 stops the behaviour of the index reset while filtering, but it's definitely not a solution. I can understand the reason behind, as we prefer to asynchronously compute the filter again on a change of items, without showing old matches that might not be accurate anymore.
With ccmanager I have a backend refresh system that updates list items from time to time. It uses SetItem to update the item when it is changed and uses Index to get the index of the item to replace. However, when filtering is used, Index returns the index of the selected filtered item and not which index the item holds in the slice of all items.
To be backwards compatible, I'd propose a "IndexOfSelectedItem" variable to get the index of the currently selected item in the slice of all items.
Or am I missing something here?
The text was updated successfully, but these errors were encountered: