matrixfurry.com
The open source OpenXR runtime
doc: a->an
Part-of: <https://gitlab.freedesktop.org/monado/monado/-/merge_requests/2322>
+2
-2
doc/CHANGELOG.md
+2
-2
doc/CHANGELOG.md
···
470
470
([!2086](https://gitlab.freedesktop.org/monado/monado/merge_requests/2086))
471
471
- The runtime name is now picked up from the CMake project description.
472
472
([!2089](https://gitlab.freedesktop.org/monado/monado/merge_requests/2089))
473
-
- Add `xrt_device::ref_space_usage` function to let a `xrt_device` know if a
473
+
- Add `xrt_device::ref_space_usage` function to let an `xrt_device` know if a
474
474
reference it's powering is being used or not by any client.
475
475
([!2091](https://gitlab.freedesktop.org/monado/monado/merge_requests/2091),
476
476
[!2107](https://gitlab.freedesktop.org/monado/monado/merge_requests/2107))
···
2978
2978
- OpenXR: Correctly ensure that the application has called the required get
2979
2979
graphics requirements function when creating a session.
2980
2980
([!359](https://gitlab.freedesktop.org/monado/monado/merge_requests/359))
2981
-
- OpenXR: When a `XrSession` is destroyed purge the event queue of any events
2981
+
- OpenXR: When an `XrSession` is destroyed purge the event queue of any events
2982
2982
that
2983
2983
references to it so that no events gets delivered to the applications with
2984
2984
stales handles.
+1
-1
doc/design-spaces.md
+1
-1
doc/design-spaces.md
···
30
30
* Where do space events come from?
31
31
* **UNRESOLVED:** Probably will come from the space overseer.
32
32
* Do we map all spaces one to one, like the each `XrSpace` with an offset gets
33
-
backed with a `xrt_space`. There is going to be a limit on spaces from the
33
+
backed with an `xrt_space`. There is going to be a limit on spaces from the
34
34
point of view of the IPC layer, do we create some of them locally?
35
35
* **RESOLVED:** While you can create a offset `xrt_space`, the offsets from
36
36
from the `XrSpace`s are not expressed as an `xrt_space` this is to reduce