Aaron Suen 966ed012b2 Expose node spin data in registrations
Deprecate the old APIs that used to close over the
metadata about valid node rotations.  Now expose
this data in the node definition, and use a generic
non-closure function to handle the callback.

nodedef.spindata contains:

qty = number of allowed rotations total
cycle = table keyed on current param2 and valued with
  next param2 for next rotation
equiv = table keyed by each possible param2 (24 keys)
  and valued with canonical equivalent for that param2
2023-10-29 02:49:22 -04:00
..
2023-10-26 20:12:03 -04:00
2020-01-05 11:42:22 -05:00
2023-10-26 20:12:03 -04:00
2023-02-03 18:58:53 +00:00
2022-01-15 12:17:13 -05:00
2023-03-27 06:57:40 -04:00