Robert Lieck

Thanks @empet, this is really helpful! So the behaviour for the marker size is probably intended. I wasn't aware of that inheritance, but it makes sense. Adding `auto_play=False` is a...

@empet my issue was **not** the moving scene, but the **disappearing traces**, which is still happening in your example. But you brought up the idea of adding dummy traces. So...

@nicolaskruchten thanks for your comment. I am not familiar with the internals, but the frame traces seem to "hijack" the other traces (e.g. they take their place in the legend,...

@empet Ah, interesting, so my initial example shows a different behaviour on your machine and on mine (on mine the grid disappears, but the frames display correctly – albeit with...

Hi @leriomaggio and @timsainb, I just came across this because I was looking for _exactly_ this feature. I need some more flexibility with the embedding topology (e.g. I need to...

Thanks for your replies @timsainb and @leriomaggio @timsainb thanks for linking the notebook and good luck with the thesis writing 💪 @leriomaggio This is great! I will be off in...

There is more than that happening: 1. The marker size is somehow differently interpreted (markers change size w.r.t. passing the same size as a single value) 2. The markers have...

From trying out different values, it seems that size is interpreted as the ***radius*** if a single value is given and as the ***diameter*** if an array is given.

The border can be turned off by explicitly specifying `line=dict(width=0)` in the `marker` dict.

I am having the same/related issue in a Plotly Dash Python app. I have some rather complex "background" traces that are static and a very small, dynamically changing "indicator" trace...