Link to 'fire an input source' algorithm, explicitly construct frame by Manishearth · Pull Request #797 · immersive-web/webxr · GitHub
Skip to content
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

Link to 'fire an input source' algorithm, explicitly construct frame #797

Merged
merged 1 commit into from
Aug 15, 2019

Conversation

Manishearth
Copy link
Contributor

fixes #711

This ended up being a bit trickier than I thought; I can also do the very simple fix originally proposed.

r? @NellWaliczek

cc @ddorwin


1. Let |frame| be a new {{XRFrame}} with {{XRFrame/session}} |session| for the time the event occurred.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's a bit tedious to create the frame separately each time. I could also create the frame in the algorithm, however we may need to more strongly imply that the frame refers to poses from the time of the event, given that the algorithm is always called within a queued task (and thus the frame should not refer to poses from the time of the task)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I can see that this is a bit of a pain, but I think your logic here is sound and that this captures the intended timing well.

@toji
Copy link
Member

toji commented Aug 15, 2019

LGTM. Thanks!

@toji toji merged commit dd7465e into immersive-web:master Aug 15, 2019
@toji toji added this to the August 2019 milestone Aug 15, 2019
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.

Link "fire an XRInputSourceEvent" text to the related algorithm
2 participants