Old coordinate bug fixed itself (Fix #109)

I thought there was a bug where overlay/layer computations were being
mixed in such a way that we needed to match the named and unnamed
coordinate stringification functions. I can't find any evidence that
this is still the case.

src/core/layer.ts

@@ -1,9 +1,13 @@
+import { DEBUG } from "../util/debug";
 import { Point } from "../util/types";
 
 // Implements a lazily-evaluated, cached, immutable sparse map from coordinates to T
 
 // This is global
 const cache: Record<string, any> = {};
+if (DEBUG.stateExporter) {
+  (window as any).layerCache = cache;
+}
 
 export type Layer<T> = {
   name: string,
@@ -24,7 +28,7 @@ function unparseNamedCoord(name: string, p: Point): string {
 }
 
 function unparseCoord(p: Point): string {
-  return `,${p.x},${p.y}`;
+  return `${p.x},${p.y}`;
 }
 
 export function mkLayer<T>(name: string, func: (p: Point) => T): Layer<T> {

src/ui/gl-render.ts

@@ -376,7 +376,7 @@ export function glInitialize(ci: CanvasGlInfo, dispatch: Dispatch): GlEnv {
   };
 
   if (DEBUG.stateExporter)
-    (window as any).cache = () => _cache;
+    (window as any).renderCache = () => _cache;
 
   return {
     gl,