trafficonese

Not only, - I removed all `::` function calls - `cumsum(l)` is calculated twice, so I saved it in a vector and re-used it - created a vector `names(choices)` outside...

Great! and yes, keep `choice %in% selected` as I think its way faster anyway in most cases.

@pvictor - Another thing which is much faster. Instead of `sapply(choices, length)` you can just use `lengths(choices)` But I think most time-saving will come from the new function `selectOptions`.

Indeed, `lengths` came with 3.2.0

- Nice solution from @swnydick, which is consistently around 10 times faster for me with 500, 5.000 and 50.000 choices and gives identical results. - And using `captureOutput` as suggested...

I agree

The docs apparently were not updated, as the following functions **dont exist** anymore: - **create_edges / create_series / create_nodes** - **combine_nodes / combine_edges** But the R-examples in the package are...

I think [all those examples](https://github.com/rich-iannone/DiagrammeR-examples/) are working. And if you are in RStudio, click on a function and press F1, that will open the help page of that function with...

It seems that both layers are still active, and glify only "sees" the first one. Manually setting the first one to `active = false` with ``` L.glify.instances.forEach(e => { if...

@paragemini I managed to get it to work with the hack mentioned above, but it's not really a fix. I run this JavaScript snippet from within my shinyapp. Otherwise I...