Skip to content

Spec: Move outputContext to XRRenderState #536

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 1 commit into from
Mar 19, 2019
Merged

Conversation

toji
Copy link
Member

@toji toji commented Feb 21, 2019

Also documents the algorithm for removing the ouputContext from previously bound sessions when a new session has been associated.

@toji toji requested a review from NellWaliczek February 21, 2019 22:53
1. If |prevSession| is equal to |session| abort these steps.
1. If |prevSession| is not <code>null</code>:
1. If |prevSession|'s {{XRSession/renderState}}'s {{XRRenderState/outputContext}} is equal to |context| set |prevSession|'s {{XRSession/renderState}}'s {{XRRenderState/outputContext}} to <code>null</code>.
1. Set |context|'s [=XRPresentationContext/session=] to |session|.
Copy link
Member

Choose a reason for hiding this comment

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

If removing the output context from |prevSession| does need to be queued, does this last step also need to be waited on?

@toji toji force-pushed the spec-output-context branch from 9fc4e21 to 0875bb5 Compare February 22, 2019 23:48
@NellWaliczek NellWaliczek added this to the Next Working Draft milestone Mar 2, 2019
@toji toji requested a review from NellWaliczek March 18, 2019 16:49
@toji toji merged commit 12474aa into master Mar 19, 2019
@toji toji deleted the spec-output-context branch March 19, 2019 20:27
@AdaRoseCannon AdaRoseCannon added the ed:spec Include in newsletter, spec change label Mar 29, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ed:spec Include in newsletter, spec change
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants