Feature - continous camera movement tracking #601
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also only redraw if volume rendering is present after camera motion
|
The changes here have been integrated into #589, but 589 can be updated again based on changes from this PR |
|
Closed as #591 included these changes |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The context can be used to mark the camera continuously moving. The context will mark the camera movement as completed after 300ms using lodash debounce, and emit a signal when this happens. At the moment, only the perspective panel listens for this signal, and uses it to trigger a redraw request if volume rendering is enabled on that panel.
The actions that flag the start of a continuous camera movement are: