Hover tooltip to be shown only for visible parts of the glyph

ahassaineMar 11, 2020 #1

Hi guys,

Is there a way to make the hover tooltip only visible when I hover over a visible part of a given glyph? For now, even if I hover over a part which is hidden by another glyph the tooltip still displays which I don’t want. Any ideas on how to fix this?

Thanks,
Ali

⌁ Link to post

BryanMar 11, 2020 #2

I’m afraid there is not any good solution for this use case at present. The hover tools hit tests against every renderer it is configured for (defaults to all gyphs) and displays tooltips for every hit. You would have to update the .renderers of the tool to exclude the glyph renderer you do not want to display (and then no tooltips would appear for that glyph anywhere).

There are some relevant open issues I hope to be able to prioritize somewhat soon that would help in situations like this:

github.com/bokeh/bokeh

Store selection per-glyph before aggregating

opened 07:30PM - 22 Sep 19 UTC

bryevdv

type: task tag: component: bokehjs

Currently when a selection tool acts on multiple glyphs, we try to combine those… indices according to some policy. That's well and good, but we compute the aggregated versions "along the way" and never store the per-glyph selections. I would like to make the steps along the way more explicit. In particular, I would like to make selections for each glyph be stored independently, possibly exposed to user. And then a policy can act cleanly on these independent selection values. I would also like to add a boolean flag per-glyph that states whether there is any selection at all. This solves the issue of knowing, e.g. just whether a `Line` or `Patch` is hit, but can also be uniformly applied across glyphs.

github.com/bokeh/bokeh

Provide hit_filter property on HoverTool and TapTool

opened 11:10PM - 15 Jul 19 UTC

bryevdv

type: feature tag: component: bokehjs

`HoverTool` (edit: and `TapTool`) should gain a new property: ``` hit_f…ilter = Instance(SelectionFilter, help=""" """) ``` A hit filter is a model with an `execute` method that accepts a `Selection` as well as a renderer model. To be used in the selection manager in the inspect codepath: ``` let hit_test_result = renderer_view.hit_test(geometry) if (filter != null) hit_test_result = filter.execute(hit_test_result, renderer_view.model) if (hit_test_result != null) { ...... ``` The purpose of the hit filter is to be able to modify the initial raw hit test restult, i.e. by pruning `.indicies` down to only 1 result, etc. or it can return `null` if it wishes to cancel inspection results (no tooltips) We will provide a `TopIndicesFilter` filter that prunes down to a specified N number of results, as well as a `CustomJSSelectionFilter` that users can implement arbitrary filtering with JS snippets.

⌁ Link to post

ahassaineMar 13, 2020 #3

Thanks for this!
Would be very helpful if you could point to some examples of how to update the .renderers

⌁ Link to post