Skip to content

Fix shadowMap interactive use + renderer props update + deprecations #383

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

Merged
merged 8 commits into from
Aug 24, 2022

Conversation

vidartf
Copy link
Member

@vidartf vidartf commented Aug 24, 2022

While doing some manual test before release, some fixes for various issues were discovered:

  • When changing some shadowMap properties, needsUpdate was not being set correctly, due to a typo in the name of a method that was suppose to override its base implementation. See commit message for details about mechanism.
  • Ensure WebGLRenderer etc also applies all renderer props when acquiring a renderer from the pool.
  • Fix various deprecation warnings
  • Some example tweaks
  • Avoids an extra call to set when not needed in syncToModel (correctly checks whether object keys are set).

All renderers need to set their properties when acquiring.
This was preventing shadow maps properties from being updated correctly. What happened was:
- onChange would trigger for WebGLShadowMap model
- The base class syncToModel was called due to the typo
- `save_changes` was called, which clears the `changed` attributes etc.
- The `change` listener on `Renderer` would trigger, and try to look at the changed attributes.

There might be a benefit to wrapping that save_changes call in a "callSoon" function?
@vidartf vidartf merged commit cc7f93f into jupyter-widgets:master Aug 24, 2022
@vidartf vidartf deleted the ipyw8 branch August 24, 2022 13:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant