Freeze navigation while generating scrambles

[campos20]

Is your feature request related to a problem? Please describe.

Log in (you may use query parameter staging=true) and ask for scramble generation.

If you navigate away (e.g. for Manual Selection), you'll see just some bars.

Describe the solution you'd like

Freeze navigation (user can't click competitions or manual until the process is done).

Describe alternatives you've considered

As an alternative, Scramble Button could be a progress bar itself and if user navigates, progress is shown just on Scramble Button.

Additional context [OPTIONAL]

• Open TNoodle
• add ?staging=true to the URL.
• Hit Log In
• Pass some delegate's id (or you can use mine, 2015CAMP17)
• Back to tnoodle, add choose a competition (if the user you selected has no upcoming competition, you can force one by adding a query competitionId, like http://localhost:3000/scramble?staging=true&competitionId=AustralianNationals2020)
• Generate and navigate

If you choose freezing navigation, this won't be needed anymore.

tnoodle/tnoodle-ui/src/main/components/Main.jsx

Line 65 in d44cb84

// If user navigates during generation proccess, we still get the correct name

Also, it would be nice freezing copies, FMC buttons, MBLD cube and any other interactive field.

[shzcuber]

I'm on it

[shzcuber]

Hello,

I have the fmc buttons, mbld button, copies input, and sidebar buttons freeze when it's generating scrambles. In my forked repository, I pushed my changes on the branch feature/change-title, and then merged it with the master branch (I realized that I should've made a new branch instead of using feature/change-title only after I did my changes). Please let me know if I need to do anything more. Thanks.

[campos20]

Fixed by #632