Per-trace axis extremes #2849
Per-trace axis extremes #2849
Commits on Jul 25, 2018
-
-
- a Axes.expend clone that does not append things to ax._min/ax._max, but instead returns two arrays, a min array and max array of potential data extremes
-
add _extremes to all traces in calc
- to be filled with the results of findExtremes
-
adapt getAutoRange and doAutoRange to trace _extremes
- pass gd, to look for _extremes in gd._fullData and eventually in layout container to can expand the axis ranges
-
generalize concatExtremes for polar, splom and layout components
- N.B. sploms are linked to multiple axes per traces, so we can't rely on single 'x' and 'y' in _extremes -> use ax._id instead!
-
Commits on Jul 26, 2018
-
replace Axes.expand -> findExtremes for ErrorBars
- here we append the min/max arrays of the corresponding trace
-
🔪 ax._min / ax._max logic for rangeslider
- questionable commit, especially the part in autorange.js, but this doesn't make any test fail ?!?
-
-
adapt polar to new per trace/item _extremes
- N.B. polar is the only subplot apart from cartesian that used Axes.expand and friends.
-
-
-
-
-
-
-
-
Commits on Jul 27, 2018
-
use ax.(_traceIndices, annIndices, shapeIndices)
... to keep track of traces, annotations and shapes plotted on axis ax. Adapt concatExtremes accordingly! -
-
add bar stack visible -> autorange test & move 'b' init to setPositions
- Bar.setPositions mutate 'b' in bar trace calcdate, we need to reinit 'b' during setPositions so that we can skip calc on visible edits
-
Commits on Jul 30, 2018
-
Revert "make annotations & shapes 'visible' -> 'plot' edit type"
- we would need to coerce their xref and yref even when `visible:false`. Not worth the effort at the moment. This reverts commit 9a78013.
-
add fallback for _extremes during concat
... to handle `visible:false` annotations and shapes that do not go through calcAutorange at the moment. -
collapse trace extremes before getAutorange
... by factoring out logic from findExtremes