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
Expose the wheel zoom speed in Python #3125
Comments
@liuyxpp we are actually in the middle of a big clean-up to ensure that the properties on the python and JS side match each other. @havocp WheelZoomTool has a default for However running the test in #3099 doesn't pick up this discrepancy. Thoughts? |
Maybe the test only picks up differences in defaults not when there's missing properties? |
great spot @bryevdv, do you know why that would be? |
Why that line exists? @Havoc added that to get things working at all. Currently the client models add all kind of new attributes with abandon and most of them should not get serialized back to the server. But a few like this one should be, but were just overlooked. We should have been more careful in the first place and made client only "viewmodel" objects to store any new, extra, "not intended to be serialized" data, and and kept the main models pure and 1-1 in sync with Python (no extra attrs added). We still should do this some day.
|
Python would raise an exception at one point if it saw an unknown property... now it just warns. So I was having to mark tons of props as nonserializable. It sounds like the better fix here was to simply add the prop to Python. |
We can certainly expose the speed, but unless we can also find a way to make a given speed somewhat uniform across browsers I am dubious of the utility. But changing to |
Reopening because the PR was reverted by #4831 |
* add option to disable wheel zoom on axes * fix #3125
The sensitivity of the wheel zoom cannot be configured on the Python side. However, there is a
speed
property which can be set on the JS side. It would be better to expose this property to the Python side too.The text was updated successfully, but these errors were encountered: