Christoph Haag e03ee48dce comp: Transition to visible/focused after xrEndFrame, not xrWaitFrame ... The application synchronizes its frame loop by "by calling xrWaitFrame, xrBeginFrame and xrEndFrame in a loop." Applications can discard frames by not calling xrEndFrame. If initial frames are discarded, we should not consider the frame loop synchronized. Previously a sequence like xrBeginFrame, xrWaitFrame, xrBeginFrame, xrWaitFrame, xrPollEvent, xrBeginFrame failed because xrPollEvent the compositor emitted transitions to visible and focused but they were not emitted in the state tracker, because the oxr session had not internally tranisitioned to the synchronized state.		2020-10-31 20:14:49 +01:00
..
auxiliary	a/android: Store a native pointer in the MonadoView.	2020-10-30 18:20:35 -05:00
compositor	comp: Transition to visible/focused after xrEndFrame, not xrWaitFrame	2020-10-31 20:14:49 +01:00
drivers	d/android: Use not-deprecated API when possible.	2020-10-30 18:20:36 -05:00
include	d/android: Add Android sensors driver.	2020-10-30 18:20:35 -05:00
ipc	ipc: Add ipc_android doc group	2020-10-29 17:02:06 +00:00
state_trackers	comp: Transition to visible/focused after xrEndFrame, not xrWaitFrame	2020-10-31 20:14:49 +01:00
targets	t/oxr_android: Include library attribution/notices in "about" activity.	2020-10-30 18:20:36 -05:00
.clang-format	tests: Use project code formatting on tests	2020-06-17 17:32:23 -05:00
CMakeLists.txt	build: Switch all CMake options to XRT_... to match what's used in source.	2020-05-12 11:52:51 -05:00
meson.build	build: Enable service less build with meson too	2020-07-14 02:16:06 +02:00