Sorting time increases too quickly when sorting speed is increased during sorting

[dlarocque]

When the FPS slider is moved to decrease the FPS of a sorting algorithm being visualized, totalDelay and visualizationTime become out of sync (totalDelay > visualizationTime, which is not possible), leading to the value of Sorting Time being negative. Quick sort isn't THAT fast :)

Related to this issue, when the delay is very high at the beginning of a sorting visualization (500ms delay), the sorting time starts out initially negative.

[dlarocque]

This seems to be caused by poor design... (by me ): )
Trying to determine the time of sorting algorithms where n is a small number (<1000) is not only give a tiny number, but it will be very inaccurate since we are performing other actions in the sorting algorithm.

We can try to solve this by completely changing how the program works.

• Stop using SwingWorker / Make the program no longer multi-threaded.
• Complete the sorting algorithm first, while storing all of the swaps / arrays in a table, then drawing all of those swaps.

• Storing these swaps can make the time inaccurate again...

I'm just going to remove the sorting time label in the performance label and just show Visualization Time :)