Easy specification of dimensions for hover tool
See original GitHub issueInstead of building an explicit hover tool to choose dimensions to show hover information for, maybe we could have a syntax such as:
tools=['hover+time|voltage']
Where +
means you are building a whitelist (what to include) and -
means it is a blacklist (what to exclude). E.g to exclude ‘time’ and ‘voltage’:
tools=['hover-time|voltage']
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (14 by maintainers)
Top Results From Across the Web
Configuring plot tools — Bokeh 2.4.3 Documentation
You can configure the crosshair tool dimensions by setting the dimensions property to width , height , or both . HoverTool#. name: 'hover'....
Read more >HOVER's 3D Technology - CertainTeed
HOVER's patented technology will provide you with detailed exterior measurements for any roofing, siding or windows projects. You can also use the 3D...
Read more >Plotting with Bokeh — HoloViews v1.15.3
To enable the hover tool, simply supply 'hover' as a list to the tools plot option. By default the tool will display information...
Read more >Hover tool improvements · Issue #1189 · bokeh/bokeh - GitHub
I know the tool architecture is changing so my terms might be a bit off. I would like configurability of tool activation methods....
Read more >Tooltips - Material Design
Tooltips display informative text when users hover over, focus on, or tap an element.
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
Sounds like we could support a general mechanism for Bokeh tools where we generalize our
tools
parameter to accept tuples, i.e. something liketools=['tool1', ('tool2', settings2), ('tool3', settings3)]
. To implement that per tool, we’d register a handler for that tool that maps the given settings into configuration for that tool. For hover, what the handler would do is accept a string (i.e., HTML template), list (i.e., list of dimensions), or dict (i.e., list of dimension:formatter pairs) specification, and would map that into thetooltips
argument of HoverTool. Other tools could be configured similarly. Something for you to attack, @jlstevens ?That final suggestion seems pretty reasonable to me. The only think I would like is for there to be a clear mechanism that maps a string (e.g. ‘pan’, ‘wheelzoom’, ‘hover’) to a Bokeh tool model or the tuple format (e.g.
('hover', ['col1', 'col2'])
which should also support the HTML template). I’m not sure what would be customized for other tools but I would hope to make this mechanism general for all the tools…