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
I believe this is (another) side-effect of our dataScale hack (more on that in: #2646) where sizeref: 1 should correspond to two cones of max norm at the minimal adjacent position just touching each other. But by the time gl-cone3d computes the max length the x/y/z positions and u/v/w vectors are scaled meaning that we should also scale sizeref before passing it to gl-cone3d. Doing this might be tricky as x/y/z and u/v/w are vectors and sizeref is a scalar, but hopefully there's a way to do so in plotly.js.
See https://codepen.io/etpinard/pen/gKMJyZ that has the default
sizemode
andsizeref
and compare with https://codepen.io/etpinard/pen/eKzawB?editors=0010 that hassizeref: 10
. Cone should always be visible using the defaultsizeref
so something is off.I believe this is (another) side-effect of our
dataScale
hack (more on that in: #2646) wheresizeref: 1
should correspond to two cones of max norm at the minimal adjacent position just touching each other. But by the timegl-cone3d
computes the max length the x/y/z positions and u/v/w vectors are scaled meaning that we should also scalesizeref
before passing it togl-cone3d
. Doing this might be tricky as x/y/z and u/v/w are vectors and sizeref is a scalar, but hopefully there's a way to do so in plotly.js.If so, fixing this should also fix #2700
The text was updated successfully, but these errors were encountered: