Avoiding "-1" on player number - bug and workaround
Posted: Sat Apr 25, 2009 1:39 am
We have identified a bug in the current version (1.01.06), and the same bug also exists in the release awaiting approval (1.50.14).
If you are editing a Roster in Team Manager or a Lineup when going to score a game, there is a chance that Jersey #'s for some players may change to -1, position will be set to nothing, and batting will be set to nothing as well.
To make sure this does not happen, do a quick flick/scroll through the whole team list before making a change. Once you have done this, you can make as many changes as you like without the risk of this issue.
Why is this happening? We are using a technique for saving memory recommended by Apple (only loading data when it comes into view), but it is causing a problem because when you make a change to a roster or lineup, we then save all the data back to your database. In this case, we have only loaded the players that have been seen in the list, so when writing the data back to the database, we are losing the jersey #, position, and batting flag (yes/no) for any player that was never visible in the list.
Again, the simple workaround for now is to just make sure you flick through the whole table before making a change.
This has already been fixed for our next update.
Thank you.
If you are editing a Roster in Team Manager or a Lineup when going to score a game, there is a chance that Jersey #'s for some players may change to -1, position will be set to nothing, and batting will be set to nothing as well.
To make sure this does not happen, do a quick flick/scroll through the whole team list before making a change. Once you have done this, you can make as many changes as you like without the risk of this issue.
Why is this happening? We are using a technique for saving memory recommended by Apple (only loading data when it comes into view), but it is causing a problem because when you make a change to a roster or lineup, we then save all the data back to your database. In this case, we have only loaded the players that have been seen in the list, so when writing the data back to the database, we are losing the jersey #, position, and batting flag (yes/no) for any player that was never visible in the list.
Again, the simple workaround for now is to just make sure you flick through the whole table before making a change.
This has already been fixed for our next update.
Thank you.