Number of heats should be flexible not fixed at 40.

[Tudor Holton]

The number of heats available should be flexible not fixed at 40.

A fixed 40 heats causes problems when the number of heats in an event (e.g. 100m) is more than 40.
Currently the workaround is to create a new event, but that is not ideal and works against the "Official Results" approach.

The suggestion is that:
1) A "+" button appears at the end of all existing heats. The "+" creates a new heat for the user to select.
2) No heats are created initially. (Currently it defaults to creating a heat with that number when the heat button is selected.

[Craig Mahony (cmahony)]

Actually, currently when an event is opened for the first time the buttons are shown but no heat is created. A heat only gets created if a heat button is clicked. If a user was having a sticky beak and opened an event and clicked button one and did not put in any results and heat is still crated by clicking the heat button. The next time the user opens the event the heat will actually open because it was created the previous time.

My concern over this is that we will have to link heat button creation to storage in case another user creates a heat in the same event. Currently there is a delay before a remote computer is updated with information. This could cause problems with duplicate heats and heat buttons, etc. I would like to get the application data storage working faster with a database first.

I think we need to have a discussion over this to avoid any unforseen pitfalls.

[Craig Mahony (cmahony)]

Done just prior to demo on 1/07/09.

[Ken McLean (kenmclean)]

This works nicely, however having a new heat be created when clicking the last heat number is not useful, and instead always creates one extra heat than actually needed. I will submit this as its own bug