-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Datensynchronisation #44
Comments
Also each actual row has its own specific key which is independent of the key of the data so what happens is the row key determines that that row is the same element Any actual render printing section for the rollers we iterate over the rose in the visual order using the hue or heat and correlate visual order with the correct instance of the data So those data items are then passed in as template slots variables or state to those rows in the correct order and that triggers the reprinting of those rows with the correct data The same idea for cells so we do not key these row view components with a data key with key then simply with their own specific keys as they are fixed rows for the viewport the virtualized table |
Keep a double end queue or a heap in order to keep the actual visual order of the available to be printed into the data sync
The text was updated successfully, but these errors were encountered: