Open roice3 opened 8 years ago
The biggest risk here is that losing track of the exact macro file can render the log file useless. One approach might be to include invoked macro definitions within the log files, but then there would be two sources of macros that can potentially conflict. If this is done, I think it might be best for internal macro references be done via GUIDs rather than by name or index. In no case would I want a dependence upon any external resource.
Requested from Eduard on the 4d_cubing group. He wrote:
What about a MagicTile Version which doesn't put all moves in the log-file but only the calls of the macro where a macro is used? Or is there already a newer version which does this? In the HOF the log-file-lenght could also be used instead of number of moves.