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
But i think that the most performant way has to be CSS thread (i have not done chrome performance test).
So For optimizing 50+ paths i think the best way is to manualy create the canvas layer outside the plugin, and call the antPath with the multipath (this actualy works).
And end with 1 Canvas layer and 1 svg for animation of all.
Summary: Can you add a flag that will only render the antPath ? with no solid path ?
The text was updated successfully, but these errors were encountered:
@dolpsdw are you seeing a "flashing" of the antPaths in Chrome? I have a project that is using 200+ antPaths, and it's producing a strange flashing effect when viewed in Chrome (no issue in Firefox)
Type:
Description:
Hi, i am experimenting with this plugins, i have to animate like 50+ paths and it was horrible on performance.
After going deep, i understood that the current implementation of the plugin, do 1 svg for original path, 1 svg for animated one.
I have been rewritting the plugin to work with Canvas animation #55 and find that it performs nice.
(CheckOut https://github.com/dolpsdw/leaflet-ant-path)
But i think that the most performant way has to be CSS thread (i have not done chrome performance test).
So For optimizing 50+ paths i think the best way is to manualy create the canvas layer outside the plugin, and call the antPath with the multipath (this actualy works).
And end with 1 Canvas layer and 1 svg for animation of all.
Summary: Can you add a flag that will only render the antPath ? with no solid path ?
The text was updated successfully, but these errors were encountered: