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
WIP: display_with_id #2940
base: main
Are you sure you want to change the base?
WIP: display_with_id #2940
Conversation
Depending on the content it could be important to retain zoom setting across updates, I can imagine users would try to zoom into a changing plot once in a while, which would then be jarring if it was reset. |
The most obvious behavior for users is usually the most annoying to implement.. |
Regarding an minimum viable version of this feature, 'zoom retention' could be taken care of using I'll also echo what @davidanthoff said in Slack ...
Call this toggle "Iterative plot mode," and it could live in the plot pane's "More Actions..." ellipsis. Have a hover info tag that could explain what it means with something like:
|
Instead of MIME type, would it make sense to do this via a special IOContext flag? Like passing |
Although of course MIME wouldn't need a dependency either now that I think about it. Maybe that's better then as it's more explicit. And maybe it's better if it errors instead of silently doing nothing, as otherwise one would be pushing many plots that are meant to be thrown away but then accumulate in memory. |
Another idea, how about MIME type plus NamedTuple such that there's an easy way to pass the ID. So Or is there a better way to pass the id information? |
Interesting, is it not "weird" to make a MIME type per id? Or are custom MIME types like that fair game |
It is kinda weird, yes. Note that the user doesn't actually need to care about that for anything but the |
I would like to try and advance this, I assume you haven't moved it forward because you weren't satisfied with the MIME type design, yet? To me it still seems clearer to do this via IOContexts, or did you have a specific reason why you wanted to go with the MIME route? |
ToDo: