-
Notifications
You must be signed in to change notification settings - Fork 4
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
Release/v0.5.8 #101
Release/v0.5.8 #101
Conversation
…le-drawings Interactable Drawings
This reverts commit 34862ed.
{ | ||
UndoRedoManager.Instance.savedStrokeActions.Push | ||
( | ||
(System.Action) |
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.
(Future) Do we need the System.Action wrapper?
|
See https://uofi.box.com/s/4d4nbx1l98ipoe41ko7m23kcsa36fg9g for the capture log, the build test results, additional bug and workaround notes, etc. |
VR Notes:
Spectator Notes:
WORKAROUND: it is paramount to check the status of the session connection in the people tab before pressing Start Capture. IT CANNOT say VR Bug: Drawing messages aren't always received after reconnection Steps to reproduce:
|
Please see commits in #99 to understand some bug fixes finished in release/v0.5.7. |
|
@Barasakar I'm just going to bypass our typical review process and merge this myself. Please let me know if you find anything wrong in the repo, and we can recuperate from there. |
@Barasakar This is everything I do after each testing session. It's kind of a lot TBH so if you find a way to simplify that then go right ahead! |
v0.5.8 Release: Interactable Drawings, Refactored DrawingInstanceManager
Interactable Drawings
Please see #100
Refactoring
Renamed Draw_Refresh to ReceiveDrawUpdate and refactored into the following functions:
Combined lineRenderersInQueue and allStrokeIDValidator into a single dictionary, lineRendererFromID, and made sure any uses of that dictionary went through new functions that talk directly to the ID. Did not change the overall functionality.
De-coupled DrawingInstanceManager from NetworkObjectsManager.
Added various warnings for edge cases, like trying to move a line that exists in your client but not in someone else's (because you drew it before they joined).
The motivation is that we should now be able to more easily debug the content. In particular, we can address the warning in the linked pull request and display the drawing line / stroke ID.
Type of change
How Has This Been Tested?
Test basic single-client transforming of drawings
Test basic synchronized transforming of drawings
Note that undo only applies to the draw action and erase action, and not to any transform actions.
[Duplicate all of the above for each distinct feature / bug fix / etc.]
Test Configuration
Checklist:
My code follows the style guidelines of this projectModified from this article:
Phillip Johnston, “A GitHub Pull Request Template for Your Projects - Embedded Artistry,” Embedded Artistry, Aug. 04, 2017. https://embeddedartistry.com/blog/2017/08/04/a-github-pull-request-template-for-your-projects/ (accessed Jul. 22, 2021).