-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update to use new SceneViewer events #88
Conversation
selectedEntityValue && selectedComponentValue | ||
? { | ||
[DataBindingLabelKeys.entityId]: selectedEntityValue, | ||
[DataBindingLabelKeys.componentName]: selectedComponentValue, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we set the selected propertyName?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we did not use it to match the data binding, so I just removed it
} | ||
: undefined; | ||
|
||
const selectedNode = getSceneNodeByRef(getSelectedSceneNodeRef() || ''); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we always use nested function calls to get the selectedNode? What use case is there to use just one of these functions?
Seems like we don't need to return both from useSceneComposerApi
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
getSceneNodeByRef
should be a useful function to be exposed on it's own, so I just make them separate ones
de04a21
to
e157bdf
Compare
Known bugs for camera position and video playback mode. to be fixed with next PR |
No description provided.