As seen in the attachements, the program fatally crashes when erronous save information is parsed by the program during initialisation. In this case, I exited the program to save the datafile, then opened it and entered random data in a single entry, then saved the file and restarted the program.
While this may not affect most users, users who enter data manually wrongly, or who experience file corruption are likely to be significantly affected by this bug/prevented from using the program entirely, unless they figure out that they need to delete the file/fix the erronous data entries, which is very unlikely.
A suggestion is to add exception handling for this scenario to allow for functionality to continue, then provide a UI prompt to the user to inform them of the malformed datafile.
As seen in the attachements, the program fatally crashes when erronous save information is parsed by the program during initialisation. In this case, I exited the program to save the datafile, then opened it and entered random data in a single entry, then saved the file and restarted the program.
While this may not affect most users, users who enter data manually wrongly, or who experience file corruption are likely to be significantly affected by this bug/prevented from using the program entirely, unless they figure out that they need to delete the file/fix the erronous data entries, which is very unlikely.
A suggestion is to add exception handling for this scenario to allow for functionality to continue, then provide a UI prompt to the user to inform them of the malformed datafile.
Labels:
type.FeatureFlawseverity.Mediumoriginal: Yvorm/ped#5