-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improve DataFrame / plotting tooltips #1118
Comments
@petersteneteg @ResearchDaniel @AnkeAnke comments? |
how many columns are we talking about? |
I think one might have a string property for a format string for the tooltip in the processor. And we might have some predefined names for the header/data for each column.
Or something along those lines. With some resonable defaults. |
Different plots may want to display different details.
A format string could also be useful so that one can decide the number of decimals and add the unit for example. |
I don't think marking data frame columns is a good way to go. How would you encode that in a csv file for example? Makes little sense to put the rendering semantics into the data. Different renderers might also want to show different information. |
Agree, to clarify I meant that each plot decides which columns to show. That could be done by marking the columns in the GUI with optional formatting using a new “tooltip property” |
ok. I would want to avoid having to make a long list if bool properties that is just show in tooltiip or not, that seems very verbose, and since the problem was having many columns, the solution should ideally not be linear with the number of columns... |
I like @petersteneteg's suggestion with the formatting string. Maybe add a button to include all columns (kind of the "default" state). Alternatively, a BoolProperty "Show All Columns in Tooltip". |
20+ columns. In my case I had 30 columns. |
Here is how Vega does it (per plot, specify which columns along with its type, optional title): |
A dropdown menu that prefil the format string with some resonable default might be nice. How does 30 lines fill the entire screen? One can also add multiple "columns" to the tool tip to allow show more content...
In a multi line string property. That would then be matched and applied for each column, that would be both small, easy to use, flexible, and scale to very many columns. |
splitting that in 2-3 columns might be useful... unless the data frame has pointless data in it. I think it often is quite nice to be able to see all the data for a point... in many cases you don't know beforehand which data will be the relevant one... |
Agreed. But in the specific case you want to limit them. |
When plotting a DataFrame and hovering a data point, the tooltip shows data from all columns. In case of large data frames this becomes excessive and results in tooltips covering most of the screen.
Suggestion:
The text was updated successfully, but these errors were encountered: