From f9e281b2ffd7f8559933eb2d19b5415f7264ef93 Mon Sep 17 00:00:00 2001
From: joni <johnfshaughnessy@gmail.com>
Date: Fri, 30 Mar 2018 02:54:17 +0200
Subject: [PATCH] Remove comment
---
src/components/hand-poses.js | 10 ----------
1 file changed, 10 deletions(-)
diff --git a/src/components/hand-poses.js b/src/components/hand-poses.js
index d6a54745e..2773475ff 100644
--- a/src/components/hand-poses.js
+++ b/src/components/hand-poses.js
@@ -90,16 +90,6 @@ AFRAME.registerComponent("hand-poses", {
}
});
-//TODO: Should I use the previous pose?
-// Argument against: The previous pose should already be given to
-// hand-poses update function, except in cases where
-// a remote user has updated their poses locally at
-// a faster rate than the network tick. In this case,
-// I don't know whether knowing the most-recent previous
-// pose is better than using the most-recently known pose.
-// In either case, the resulting animation seems fine, and
-// passing around only the most recent pose info saves
-// bandwidth and makes the code shorter.
AFRAME.registerComponent("hand-poses-controller", {
schema: {
left: { type: "selector", default: "#player-left-controller" },
--
GitLab