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
Many visualization types have either keystrokes or mouse actions that trigger different functionality, and much of this is currently undocumented and may not be obvious (e.g. clicking to select nodes, using arrow keys to change color map).
We should add functionality for a ? icon as a small button, maybe in the upper right of a visualization, next to the Actionsbutton.
This should be an endpoint that allows a key-value specification of buttons/keys and associated actions, which visualization types can then provide. For example, for a line we might have:
Would be very nice to somehow replace the key strings with icons (e.g. for left-arrow), but that can wait.
It's also not clear whether to add this to the visualization only as displayed in the lightning notebook or in a way that can be embedded, @mathisonian ?
The text was updated successfully, but these errors were encountered:
Many visualization types have either keystrokes or mouse actions that trigger different functionality, and much of this is currently undocumented and may not be obvious (e.g. clicking to select nodes, using arrow keys to change color map).
We should add functionality for a
?
icon as a small button, maybe in the upper right of a visualization, next to theActions
button.This should be an endpoint that allows a key-value specification of buttons/keys and associated actions, which visualization types can then provide. For example, for a line we might have:
For images
In some cases we'll have groups of buttons that have similar functionality, so probably want to be able to be concise, as in:
Would be very nice to somehow replace the key strings with icons (e.g. for
left-arrow
), but that can wait.It's also not clear whether to add this to the visualization only as displayed in the lightning notebook or in a way that can be embedded, @mathisonian ?
The text was updated successfully, but these errors were encountered: