You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MODAQ was designed for handling thrown out tossups in the old way, which was that a replacement question would be read at the end. Most tournaments now have a packet of replacement questions, which means that throwing out a question should instead prompt for a replacement question, and then that question is tracked separately.
This needs a lot of design work.
The text was updated successfully, but these errors were encountered:
User clicks on the X or the menu button to throw out a question
A dialog appears asking the user how they would like to replace the question:
Go to the next available question
Insert a replacement question
There is a button for loading the packet, and a spinner for which question to pick from the packet
One challenge here is handling the case where one team negs on a question, and then a replacement is read. You have to keep both questions around, but MODAQ currently assumes that there is one tossup per question. We have to change the internal state to indicate when a question is just a replacement, which will make the logic more complicated.
MODAQ was designed for handling thrown out tossups in the old way, which was that a replacement question would be read at the end. Most tournaments now have a packet of replacement questions, which means that throwing out a question should instead prompt for a replacement question, and then that question is tracked separately.
This needs a lot of design work.
The text was updated successfully, but these errors were encountered: