View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003135||3 - Current Dev List||Bug||public||2019-01-29 08:43||2019-02-02 23:08|
|Target Version||Fixed in Version||22.214.171.124|
|Summary||0003135: Logbook's MessageDate() function isn't useful|
|Description||There's code in the Logbook for a global function named MessageDate(), along with some supporting friends. The implication is that the function will log diagnostic information to the Logfile, but the function actually just calls the Windows OutputDebugString() API to write to an attached debugger.|
This function isn't useful. It should be replaced with calls to the regular Logfile window so users can actually benefit from the logged information.
The function is mostly used from the Logbook's ALE window, but a few other call sites exist. Fixing the implementation to use the Logfile window will have the immediate benefit of logging progress and errors during callsign lookups performed from the ALE window.
|Tags||No tags attached.|
This checkin removes the MessageDate() calls. Most were converted into AddLogfile() calls, which become visible to the user. A few are AddDebug() calls; one or two were just eliminated.
An immediate benefit will be that logging messages appear in the LogFile tab during Callsign lookups, so some insight into the operation of the feature is now available.
||I'll accept this as complete.|
|2019-01-29 08:43||K7ZCZ||New Issue|
|2019-01-29 10:06||K7ZCZ||Relationship added||related to 0003001|
|2019-01-29 10:07||K7ZCZ||Assigned To||=> K7ZCZ|
|2019-01-29 10:07||K7ZCZ||Status||new => resolved|
|2019-01-29 10:07||K7ZCZ||Resolution||open => fixed|
|2019-01-29 10:07||K7ZCZ||Note Added: 0007116|
|2019-01-29 22:47||K7ZCZ||Fixed in Version||=> 126.96.36.199|
|2019-02-02 23:08||WA9PIE||Status||resolved => closed|
|2019-02-02 23:08||WA9PIE||Testing||Not Started => Not Tested|
|2019-02-02 23:08||WA9PIE||Note Added: 0007234|