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
{{ message }}
Repository navigation
Possibility to change visibility of a Feature without sequential removing/adding it to map #1051
When I add a lot of features (in my case GeoJsonFeature) via Layer.addFeature() the adding process becomes too slow (every sequential addFeature() is slower then previous due to amount of objects already drawn on the map).
For this I've found a workaround: first add all the objects invisible and than bulk set the visibility. This works much faster.
When using maps utils and GeoJsonLayer if I add objects using GeoJsonLayer.addFeature() I CAN initially set visibility to false, but than I CANNOT set it to true without removing and then adding the object itself with a new style (even if the #1050 will be fixed).
Please, add a possibility to bulk change visibility of all features in layer and to change visibility of individual feature.
changed the title [-]Possibility to change visibility of a Feature without removing/adding to map[/-][+]Possibility to change visibility of a Feature without sequential removing/adding it to map[/+]on Jan 8, 2022
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!
Activity
[-]Possibility to change visibility of a Feature without removing/adding to map[/-][+]Possibility to change visibility of a Feature without sequential removing/adding it to map[/+]stale commentedon Jun 12, 2022
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!
stale commentedon Jun 18, 2023
This issue has been automatically marked as stale because it has not had recent activity. Please comment here if it is still valid so that we can reprioritize. Thank you!
ryust commentedon Jun 18, 2023
Not stale