Closed AnselChang closed 1 year ago
Name | Link |
---|---|
Latest commit | 8da71a76d1b546159bed4368703702a9905f1ab2 |
Latest deploy log | https://app.netlify.com/sites/pmks/deploys/64b7341ec0eae9000826b3e6 |
Deploy Preview | https://deploy-preview-116--pmks.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I feel like it's super close but not quite there. But maybe this is good enough? Will talk more during 7/3 meeting
(Also this fixes #36, not #48)
Wait for special case for binary links before merge
Looks great! Need @AlexG1031 to merge with his PR.
Merging with #123 since Alex pulled this code into his branch
Fixes #48
After two really convoluted attempts, third solution is simply just finding the offset in which the joint moved, dividing it by the number of joints in the link, and offsetting the force vector by that amount.