Minor update to how the TimeClock checks for whether the worker is present or not. Due to the 24-hr processing mechanism, it had been looking for punches in the past 10 hours to verify that the worker was present. Well, some people apparently have 10-hr shifts, so this was updated to look at 12 hours instead. Will see if that causes problems or not.
Auto-Punch-Out when punching with a fingerprint now is a bit smarter about 24hr shifts. Hopefully smart enough to dispense with the troubles that such things have been causing.
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.
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.
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).
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.
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.
TimeClockVersionDate not displayed on the startup screen correctly.
Buzzer System
Added second exception for the buzzer system to hopefully eliminate exception errors. Seems these exceptions should not be generated, but all reports indicate that the buzzers are working, so not sure why an exception is generated in the first place. Odd, really.
TimeClock logs are now incorporated into the exception report that is uploaded to Mantis (or emailed directly).
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.
Changed keyboard shortcuts to Shift-Q and Shift-E for quitting the app and generating a test exception.
Fix for ERR-BUZZ situation when configuring a TimeClock to use the COMPUTERNAME as the TimeClock number. The 'TC' was being passed as part of the TimeClock number in the query, resulting in a failed query.
Updated related code to update internal TimeClock number references that occur at time of TimeClock initialization but may not have been reset when the TimeClock number changed later in the startup process.
If the TimeClock is started on a computer which has a NetBIOS name formatted as TCxyz, then as the TimeClock starts, it will automatically renumber itself to xyz instead of whatever default TimeClock number is passed to it as the first parameter.
Various internal changes were made to support (1) above, including updates to the log entries to reflect this condition.