You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We need to come up with an intuitive way to set the parent device a given overlay.
Sticking overlays to devices is already handled in auto_movement.
All we need to do is set the OverlayState's spawn_point, spawn_rotation and relative_to.
Active overlays are stored in OverlayContainer, which is normally only accessible from the backend's main loop. However, overlay states can be manipulated from anywhere where AppState is available, by app.tasks.enqueue'ing a TaskType::Overlay. Example here.
The text was updated successfully, but these errors were encountered:
We need to come up with an intuitive way to set the parent device a given overlay.
Sticking overlays to devices is already handled in auto_movement.
All we need to do is set the OverlayState's
spawn_point
,spawn_rotation
andrelative_to
.Active overlays are stored in
OverlayContainer
, which is normally only accessible from the backend's main loop. However, overlay states can be manipulated from anywhere whereAppState
is available, byapp.tasks.enqueue
'ing aTaskType::Overlay
. Example here.The text was updated successfully, but these errors were encountered: