After implementing the hints feature for the cross (xcross) solutions #256 , I've noticed that the timer is slowing down after each resolution. It's noticeable that the frames per second (FPS) are decreasing while the timer is running.
I think it's because after the state refresh, it is trying to generate new solutions even when not needed because the timer is active. Also, this feature has expensive CPU requirements.
After implementing the hints feature for the cross (xcross) solutions #256 , I've noticed that the timer is slowing down after each resolution. It's noticeable that the frames per second (FPS) are decreasing while the timer is running.
I think it's because after the state refresh, it is trying to generate new solutions even when not needed because the timer is active. Also, this feature has expensive CPU requirements.