Merge branch 'release/0.2.3'

Changelog.md

@@ -1,3 +1,6 @@
+# 0.2.3
+Fix #3. When a grid is present, snap the projected destination point to the center of the grid. This keeps the distances consistent for different cardinalities. Rounding still occurs with grid measurements such that adjacent squares may have the same measured 3-D distance despite appearing to be closer/further from the origin point. 
+
 ## 0.2.2
 Update manifest for libruler dependency to point to correct JSON URL. Fixes #2.
 

scripts/segments.js

@@ -164,13 +164,25 @@ export function elevationRulerDistanceFunction(wrapped, physical_path) {
 
   physical_path.destination = ProjectElevatedPoint(physical_path.origin, physical_path.destination);
   delete physical_path.origin.z;
+  delete physical_path.destination.z;
+
+  // if we are using grid spaces, the destination needs to be re-centered to the grid.
+  // otherwise, when a token moves in 2-D diagonally, the 3-D measure will be inconsistent
+  // depending on cardinality of the move, as rounding will increase/decrease to the nearest gridspace
+  if(this.measure_distance_options?.gridSpaces) {
+    // canvas.grid.getCenter returns an array [x, y];
+    const snapped = canvas.grid.getCenter(physical_path.destination.x, physical_path.destination.y);
+    log(`Snapping ${physical_path.destination.x}, ${physical_path.destination.y} to ${snapped[0]}, ${snapped[1]}`);
+    physical_path.destination = { x: snapped[0], y: snapped[1] };
+  }
+
+
   log(`Projected physical_path from origin ${physical_path.origin.x}, ${physical_path.origin.y} 
                                      to dest ${physical_path.destination.x}, ${physical_path.destination.y}`);
 
   return wrapped(physical_path);
 }
 
-
 /* 
  * @param {number} segmentDistance
  * @param {number} totalDistance