Open droumis opened 1 year ago
This seems to be because there is a shared c
kdims
between the neighbor_b
and neighbor_r
. Where only neighbor_b
has set the c
axis to be inverted. A MRE could be this:
import holoviews as hv
hv.extension("bokeh")
data = (range(5), range(5))
plot1 = hv.Points(data, kdims=["c", "b"])
plot2 = hv.Points(data, kdims=["a", "c"]).opts(invert_yaxis=True)
plot1 + plot2
And with (plot1 + plot2).opts(shared_axes=False)
:
Maybe an option like this hv.Points(data, kdims=["a", "c"]).opts(shared_axes=["a"])
could be a way to solve the issue.
This is also a problem when you use a parent heatmap with a tap stream to drive a child plot as in https://discourse.holoviz.org/t/how-to-keep-yaxis-of-heatmap-inverted-after-tap/7107.
ALL software version info
Bokeh: 3.2.0 HoloViews: 1.16.2.post36+g99a3f2079-dirty Panel: 1.2.0
Description of expected behavior and the observed behavior
Invert_yaxis is not working without setting
shared_axes=False
, and since I need to invert the y-axis of one plot in a layout while keeping the linked interactivity intact, I can't useshared_axes=False
.Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
shared_axes=True
shared_axes=False