-
Notifications
You must be signed in to change notification settings - Fork 224
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
Support for trait _view_count #481
Comments
Interesting. I didn't know that the existed. I don't see a strong reason not to support it. Though it may be hard to keep track of when a view is no longer displayed? @martinRenou do you have any thoughts on this? I'd say my current position is that I would be happy to review a PR implementing this so that we can decide if there are any tradeoffs - but suspect that there's no harm in implementing this. |
oh wait, is all we have to set it equal to |
Thanks for opening an issue. I don't think this is specific to ipympl, it seems it has been added in ipywidgets in jupyter-widgets/ipywidgets#1232.
Probably, there is a check for it to be a number here. I'd personally say that users of ipympl shouldn't need to access this property (after all it starts with an underscore). But I actually didn't know this was a thing. We can probably use this to cleanup figures on the backend. What do you think @ianhi ? |
That’s exactly the use-case I was going for here, but it that would be possible to do directly in ipympl then it would be even better of course |
Unfortunately such a logic would break if there are multiple clients. |
The trait _view_count does not seem to populate on the canvas (always None). Is it not supported for ipympl?
The text was updated successfully, but these errors were encountered: