07-06-2021, 07:48 AM
Hi,
1) Yes that was a bug in the code of the stacking state which was not detected when used on the edges. Now Fixed, will be in the next release.
2) For the state, I assume that's because the order of your actions in the move is not correct, just 2 examples here:
3. [(Add Ball1 to 51/0), (Remember Value 'null' 100), (State Edge 100/0=2), (Insert Line1 to Edge 100/0)]
4. [(Add Ball2 to 49/0), (Remember Value 'null' 100), (State Edge 100/1=3), (Insert Line2 to Edge 100/1)]
You are setting the state before inserting the edge. So the state becomes 0 after applying this set of actions.
I also advise you to give a name to the values you are remembering in order to have a clearer set of remembered pieces.
3) If you just want to have different rotations of any kind like you did for the svg used for "Line", yes the state is the right solution.
Regards,
Eric
1) Yes that was a bug in the code of the stacking state which was not detected when used on the edges. Now Fixed, will be in the next release.
2) For the state, I assume that's because the order of your actions in the move is not correct, just 2 examples here:
3. [(Add Ball1 to 51/0), (Remember Value 'null' 100), (State Edge 100/0=2), (Insert Line1 to Edge 100/0)]
4. [(Add Ball2 to 49/0), (Remember Value 'null' 100), (State Edge 100/1=3), (Insert Line2 to Edge 100/1)]
You are setting the state before inserting the edge. So the state becomes 0 after applying this set of actions.
I also advise you to give a name to the values you are remembering in order to have a clearer set of remembered pieces.
3) If you just want to have different rotations of any kind like you did for the svg used for "Line", yes the state is the right solution.
Regards,
Eric