Mantis

1. Pretty major update to many things.  First up, the code that draws the list of activities was updated.  Seems that the labels were all overlapping one another, making the drawing of the menu excruciatingly slow even on modern computers.  Nice and fast now, just by trimming the size of the labels.
2. Hid everything to do with 'messages' appearing at the top-right of the TimeClock - they weren't being used, and just interfered with the screen updates.
3. Updated Checklist system.  Bit of an overhaul really.  Now properly supports multiple checklists, and handles things better when multiple checklists are available, no checklists, checklists without questions, and so on.  Pretty major overhaul of how checklists are started here.
4. Changed the RESTART mechanism for upgrades, hopefully will dispense with the endless looping upgrades after a new version is installed that needs to be deployed more quickly.
5. Fixed some miscellaneous bugs in code that comes up from time to time - moving around RunQuery invocations so that they are closer to the query processing.
6. Changed the Mantis interface to add the Database/TimeClock number to the BugAccount field to make it easier to see which TimeClock is affected.

General

1. Updated EurekaLog Mantis interface to incorporate a custom field to contain the username logged in to the app.  Normally Mantis tracks things like the username logged into Windows, but of course this is not the same thing, and the actual username wasn't appearing anywhere in the bug report aside from potentially the parameters used to launch the program, which can be changed at login time.

General

1. Fixed problem with attaching log files (semi-colon-delimited list instead of comma-delimited) so now both TimeClock logs are sent in case of an exception.
2. Changed back to using SSL for Mantis connection.  For whatever reason, this means that the XP exceptions aren't sent to Mantis but come via email.  Hopefully this also means that the error message is not displayed.  Guess we'll find out tomorrow.
3. Removed one of the Buzzer exceptions that is actually an error that needs to be reported (deivce not opened vs. can't write to D0... The latter is ok, the former not so much).

General

1. Mantis connection changed from SSL to non-SSL as the SSL connection doesn't seem to work when connecting with XP clients.  Likely due to a lack of support for SSL in older versions of Windows.  Same issue with Win2K, but that didn't work no matter what...  EurekaLog support says Win2K never supported any kind of SSL, so there you go.
2. Part of the reason for (1) is that exceptions put up a text message when sending via email, which is obviously undesirable, but not code that is accessible.  When sending reports via Mantis, this doesn't happen, and we want reports to go via Mantis anyway, so hence the extra work here.  Can't really do this with Win2K anymore it seems, but down to the last two Win2K machines anyway, so hopefully a non-issue.
3. Minor update to formatting of exception emails.

General

1. TimeClock logs are now incorporated into the exception report that is uploaded to Mantis (or emailed directly).
2. New release of EurekaLog seems less functional on older platforms for some reason (sending mail instead of logging into Mantis).  Updated mail information to be more clear.
3. Changed keyboard shortcuts to Shift-Q and Shift-E for quitting the app and generating a test exception.

General

1. Application error notifications (exceptions) are now sent directly to Mantis, the tool 500 Foods uses to keep track of these kinds of issues.  Previously these were sent as emails.  EurekaLog handles the brunt of this kind of thing.
2. The previous email mechanism is now setup as the fallback error notification system in case the Mantis website isn't working (http://www.500foods.com/bugs).  Also handled by EurekaLog.