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
Return boolean from fill methods #46
Conversation
@@ -301,9 +301,9 @@ XRFrame {#xrframe-interface} | |||
<pre class="idl"> | |||
partial interface XRFrame { | |||
XRJointPose? getJointPose(XRJointSpace joint, XRSpace baseSpace); | |||
void fillJointRadii(sequence<XRJointSpace> jointSpaces, Float32Array radii); |
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.
unsure if this one needs to be a bool too
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.
Might as well, for consistency. It's not going to be as frequently used as the return value from fillPoses, but it'll definitely bite someone if the return value is different between them.
Should the boolean be |
/agenda to discuss if this is necessary |
😁 More seriously, though, I have an inclination to say that it should return |
That sounds good to me! |
That makes this great for hands, but more annoying for anchors, where a false value would still mean you need to iterate through it, but maybe filtering it. |
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.
I'm ok with returning false if any pose or radius fails to resolve.
Flipped the return value to be "if all are valid" instead of "if any are valid" |
Okay, there seems to be consensus on merging this, and the radius thing can be improved after we fix #46 . |
This lets us do things like
Another part of #37, was missed in #44
Preview | Diff