When a user presses buttons to make rotations on the rubik's cube, they could mess up what the Solve class was working on. This could create problems if the cube is in a certain state, and then all of a sudden, its conditions don't match the state it was in before the user interfered. Will need to develop a way for the Solve class to determine what state its in given the first face it wants to get, and the current state of the Rubik's Cube. This method should then be called every time the user presses a button.
When a user presses buttons to make rotations on the rubik's cube, they could mess up what the Solve class was working on. This could create problems if the cube is in a certain state, and then all of a sudden, its conditions don't match the state it was in before the user interfered. Will need to develop a way for the Solve class to determine what state its in given the first face it wants to get, and the current state of the Rubik's Cube. This method should then be called every time the user presses a button.