-
Notifications
You must be signed in to change notification settings - Fork 494
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
HITL - Add GUI rendering wrapper. #1838
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good.
I was thinking about ways to reduce the API forwarding/mirroring.
Talking to @0mdc we concluded that this intermediate class will have expanded function variable set and a branched implementation for client-side interface, so this mirror is a lesser of two evils for now.
…awer. Add accessor for internal line renderer. Remove networking placeholder. Fix typing.
e5ef51e
to
af89e28
Compare
* Add GuiDrawer class. * Change gui_drawer creation flow. Change line renderer calls to gui_drawer. Add accessor for internal line renderer. Remove networking placeholder. Fix typing. * Minor fixed. * Adapt remaining code to use gui_drawer. * Add comments. * Fix typing and typos.
* Add GuiDrawer class. * Change gui_drawer creation flow. Change line renderer calls to gui_drawer. Add accessor for internal line renderer. Remove networking placeholder. Fix typing. * Minor fixed. * Adapt remaining code to use gui_drawer. * Add comments. * Fix typing and typos.
Motivation and Context
This adds a wrapper for
DebugLineRender
, which also supports networking viaClientMessageManager
.DebugLineRender
isNone
(headless mode), server rendering is skipped.ClientMessageManager
isNone
(local mode), remote rendering is skipped.Rendering for multiple clients would be supported by either adding a "destination" parameter to
GuiDrawer
functions (relayed toClientMessageManager
), or carrying an array ofGuiDrawers
andClientMessageManagers
. I think that the former would be simpler in the long run.How Has This Been Tested
Tested in all apps along with the Unity mouse/keyboard client.
Types of changes
Checklist