trafficonese

I think thats the same problem as #48. I think the main problem is that the remove functions dont work correctly.

If we expose the option `preserveDrawingBuffer` and set it to TRUE the screenshot works with `addEasyprint` and `screenshot`, but somehow `mapshot` doesnt work. No, I didnt try webshot2 yet.

Indeed, `webshot2` also works, even with `preserveDrawingBuffer = FALSE`.

This is currently not supported in the underlying library. If you want that feature, you probably should open an issue at [Leaflet.glify](https://github.com/robertleeplummerjr/Leaflet.glify).

I think that problem might come from the upstream repo, which is not fully removing the glify instances. (see this [issue](https://github.com/robertleeplummerjr/Leaflet.glify/issues/11)) In the browser console you can see that `L.glify.instances`...

If those are the only polygons you are plotting, you could remove the instances yourself with `shinyjs`. In the ui you need to include `useShinyjs()` and after the `leafletProxy` call...

I would keep this issue open as this is more of a dirty hack than a proper fix. If multiple layers are included and the one to be removed is...

Maybe this [package ](https://github.com/eddelbuettel/rcppkalman) could help with performance?

It might be worth a try to test the functions and benchmark them with the current solution. For now, I was testing the given example and found that it's actually...

I am having the same problem. Since the `base::system` call works, I tried to rewrite my own small `orca` function with `base::system` instead of `processx::run` and it works fine. p