You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand that in "standard" notation, double moves aren't usually inverted. But for execution, it can be helpful to distinguish double turns from prime double turns. It would be great if there was an option, something like { allowDoublePrime: true/false }, with default false, that allows for normalizing with execution.
I'm going to fork this project and implement this change. I'll comment here / make a pr when the change is made in case you want to include this functionality in the project.
The text was updated successfully, but these errors were encountered:
I'm not sure about what you really want, anyway, notations like U2' are already supported (without any options). There is no restriction about the order of primes and numbers.
Right, what I meant, was it would be nice to optionally allow the prime to persist after normalization, like this: normalize("U2'", { doublePrimeMoves: true }); // => "U2'"
The reason being, imagine that I want to preserve how an algorithm is executed. Currently, the detail of the turn being prime would be lost through normalization.
bnat1
changed the title
Feature request: optionally allow double prime moves. For example: U2'
Feature request: optionally allow primes to persist through normalization on double turns. For example: U2' => U2'
Nov 21, 2018
I understand that in "standard" notation, double moves aren't usually inverted. But for execution, it can be helpful to distinguish double turns from prime double turns. It would be great if there was an option, something like { allowDoublePrime: true/false }, with default false, that allows for normalizing with execution.
I'm going to fork this project and implement this change. I'll comment here / make a pr when the change is made in case you want to include this functionality in the project.
The text was updated successfully, but these errors were encountered: