You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, great library thank you very much for your services.
I am finding myself desiring to listen to events such as drag-start and drag-end in order to programmatically control a hover tooltip that should disappear while you are dragging a row. Without that, while the mouse is hovering the row, the tooltip stays open leading to bad UX because the mouse is technically still hovering the row while it is moving around.
Tooltip is just a wrapper around vue3-popper so show=true means show, false means hide, and null means show on hover.
I might be able to figure out some other way to listen to these events, but it looks like the library is already emitting those events from within, so it would be nice to expose them out of the root component.
Thanks, have a good day.
Side note, but I'm now still examining the library code, perhaps the item template provides these events in the slot I haven't confirmed yet.
The text was updated successfully, but these errors were encountered:
Hello, great library thank you very much for your services.
I am finding myself desiring to listen to events such as
drag-start
anddrag-end
in order to programmatically control a hover tooltip that should disappear while you are dragging a row. Without that, while the mouse is hovering the row, the tooltip stays open leading to bad UX because the mouse is technically still hovering the row while it is moving around.Here is an example of what I would like:
Tooltip is just a wrapper around vue3-popper so show=true means show, false means hide, and null means show on hover.
I might be able to figure out some other way to listen to these events, but it looks like the library is already emitting those events from within, so it would be nice to expose them out of the root component.
Thanks, have a good day.
Side note, but I'm now still examining the library code, perhaps the item template provides these events in the slot I haven't confirmed yet.
The text was updated successfully, but these errors were encountered: