Bug: at startup, all times are resent to the cloud even if previously sent. The problem is in startup code which updates the eventEntry lookup cache. It not only updates the local cache but sends to the cloud. At start, it should only update the eventEntry cache.
For a large regatta, sending all data to cloud can be time consuming (and replace some times). If the regatta is marked 'finished', it takes a very long time for the GUI to stabalize.
Steps to bug:
Bug: at startup, all times are resent to the cloud even if previously sent. The problem is in startup code which updates the eventEntry lookup cache. It not only updates the local cache but sends to the cloud. At start, it should only update the eventEntry cache.
For a large regatta, sending all data to cloud can be time consuming (and replace some times). If the regatta is marked 'finished', it takes a very long time for the GUI to stabalize.