Bokeh plot with tool instances cannot be redisplayed
See original GitHub issueThis notebook illustrates issues like:
- Order of multiple
hv.notebook_extension
matters - Loosing style, size and other information during switching backends
- Replotting the same figure within the notebook causes HoverTool error with failure of the figure display
- Cannot export holomap as GIF file.
Point number 2 is expected I guess.
Could you please advise?
Issue Analytics
- State:
- Created 6 years ago
- Comments:18 (18 by maintainers)
Top Results From Across the Web
Configuring plot tools — Bokeh 2.4.3 Documentation
Configuring plot tools#. Bokeh comes with a number of interactive tools that you can use to report information, to change plot parameters such...
Read more >[BUG] PanTool can't be deactivated in grid plot #11839
It is not possuble to deactivate a tool in a grid plot. The toolbar of the grid plot is of type ProxyToolbar with...
Read more >Bokeh — Panel v0.14.2
When working in a notebook any changes to a Bokeh objects may not be synced automatically ... title="Pie Chart", toolbar_location=None, tools="hover", ...
Read more >Visualizing Data with Bokeh and Pandas
In our first Bokeh plot we saw the default Bokeh toolbar, but Bokeh allows us to customize our plot by adding new interactive...
Read more >How to change size of bokeh figure - python
If you've already created the plot, then you can use the bokeh.plotting.curplot() function to return the "current" plot, and then set its ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If you want you can open a separate issue for this, but we have in the past very deliberately decided this is not feasible.
In your example simply specify the format like this:
In future it would be great if you could separate issues into atomic chunks that can be dealt with separately with a code sample to isolate just the particular issue that is described. Issues that describe a bunch of different issues cannot be appropriately prioritized and I’ll end up closing them.
@philippjfr, thank you for your reply! Could you please point to the issues you are mentioned here:
and