James Ross, on 29 July 2014 - 12:47 AM, said:
I can't seem to get to the Subversion server to check if the fix provided is logging anything, but I would generally be happy with bad data causing either:
- A logged warning that it is being ignored/skipped
- A specific but fatal error
There's no need to make things fatal if we can cope reasonably well, e.g. by ignoring the station stop, but it must log the data problem as a warning in that case. :buffalobill:
As a software developer, I will chime in here.
Think of the end user, a non technical person who just wants to drive trains. Such a user should never see a dot net framework error. As James says, such a user should see a friendly fatal error, such as "The selected activity could not be loaded due to a defective activity definition. Please contact the author." This type of user need not know about warnings; they should be logged and swallowed.
Now there may be a more technical user such as an author, developer or other advanced user. For such a user, they may wish to see more detail. Perhaps a command line switch to alert them about initial problems that could appear on an opening dialog as soon as the activity finished loading, such as "15 warnings issued, 4 of them severe. See the log."
If not done already, such standards should be hashed out and published as firm guidelines for the project.
Thanks, John