Version 3.1.7 - June 2, 2018, STABLE Candidate Release


This release was primarily meant to be a bug fix release, but some small features were added, along with changes to help improve server configuration and operations.

New Features

  1. Added support for club specific awards. This gives the ability for clubs to add awards that are specific to the club (via the club information file). Clubs can also remove standard awards that are not applicable to that club. Any added club specific award will also add a QSL Message variable that can be used in forming the QSL message when logging a contact.

Minor Enhancements

  1. Added the ability to specify the state of the Manual Highlighter when starting up. This can be done in the Preferences dialog (under the Edit menu). Also added the ability for clubs to override the current Manual Highlighter setting for nets created for that club. Note however, that this setting is not locked, i.e. a logger can still switch back and forth after the net is started.

  2. Added support for server clusters. This only affects net creation. Instead of choosing a server to create a net on, users will be choosing a server cluster. For now, all production clusters have only one server, and the cluster name is the same as the server name. In the future this might change. NetLogger will automatically choose a particular server from the cluster, based on the total number of net subscribers on each server in the cluster, when there are more than one server in a cluster.

  3. Added some callsign slash shortcuts when entering a callsign that allows the logger to quickly set some common award status values. These work in a similar fashion to /M and /P when setting mobile or portable status when entering a callsign. The new shortcuts are /C for Combo (CMB), /Q for QRP, /S for State Capitol (SC), /T for Trucker (TRK) and /Y for YL. These short cuts don't remain as part of the callsign after they are entered. Note that entering /QRP after a callsign now sets the QRP award status, but the /QRP (instead of using /Q) will remain as part of the callsign, since some stations prefer that.

  4. Added support for a club specific default setting for the QSL Info field in the Check-ins table. If the club specifies a default value for the QSL Info field it will be used if no entry for that field is found in the club profile or via a callbook (e.g. QRZ) lookup. Note that this substitution only happens if the the Profile and CallBook Order setting for the QSL Info field includes using the club profile.

  5. Added support to immediately check for unsupported characters when entering a net name in order to provide immediate feedback, rather than waiting for the name to be rejected by the server.

  6. Added and/or modified help pages to document the above changes. Added more details regarding the club information file format, including new variables and sections to support the new club related features.

  7. Added support for updating the server configuration and the ClubInfoList.txt file from the NetLogger server. This allows updates to happen without having to release a new version of NetLogger.

  8. Added a new Subscribers column in the Nets in Progress table. This shows the current number of people monitoring the net (i.e. this doesn't include offline entries). The data was needed for support of the server cluster feature mentioned above, and it seemed worthwhile to make available.

  9. For the Linux version, some configuration changes were made to reduce external dependencies. Also, the libpng16 library was included in the distribution, since netlogger depends on it, and older Linux distributions don't typically have that version available. The net result is a Linux version of NetLogger that should install on a wider variety of both older (e.g. Debian Jessie based) and new (Debian SID "buster" based) Linux distributions.

Bug Fixes

  1. Fixed a bug where auto save check-ins file names did not have a .log extension.

  2. Fixed a bug where logger promotion failed if the net password was 2, 9, 11 or 18 characters long.

  3. Fixed a bug where some characters (e.g. the # sign) could not be used in an account password (e.g. QRZ lookup, etc.).

  4. Fixed a bug that was preventing the download of Log of the World status (which was exposed by a change on the Log of the World server).

  5. Fixed an obscure bug (that led to NetLogger crashing) that was only seen by people who manually edited their ClubInfoList.txt file.

  6. Fixed a bug where a cell in the Check-ins table that was being modified by the logger wasn't always properly locked and therefore could interfere with what the logger was entering when a server update caused a restoration of the previous value.

  7. Fixed a bug that could cause a NetLogger crash when attempting to import an ADIF file that wasn't an ADIF formatted file.

  8. Fixed a bug that could cause a NetLogger crash when using a U.S. based LoTW certificate that didn't contain a U.S. State.

  9. Fixed two Qt bugs that could lead to a NetLogger crash.

Version 3.1.6 - May 29. 2018

Closed beta test version for the 3.1.7 release.

Version 3.1.5 - July 26, 2016, Declared STABLE August 2, 2016

New Features

  1. Added a feature to allow AIM messages from a particular user (who is perhaps being obnoxious) to be ignored. This can be done either by an individual user who wants to personally ignore certain other users, or someone with logging privileges (i.e. the NCS/Logger) can cause a person to be ignored by all users (although individual users have the option of unignoring that person afterwards).

    This feature is available from the Monitors window context menu. There are two buttons, one labeled AIM Ignore which can be used by anyone to ignore a particular person, and one labeled AIM Group Ignore which is only enabled for those with Logging privileges for the current net in progress. Once a person has been ignored the entry in the monitors window will have a red background to indicate that fact. Also, once a person is set to be ignored, the AIM Ignore button will change to AIM Unignore so that individual users can stop ignoring a person. Note there is no AIM Group Unignore button, so those with logging privileges should be careful when choosing to send a broadcast ignore message.

    The ignore feature causes the chosen person to be ignored based on the users IP address. This means that if the ignored person chooses to change their callsign and rejoin the net, the effect of the ignore setting will still be set. Note however that an IP address based ignore is not perfect, and some determined people may be able to work around this. Note also that the ignore feature is implemented within the client (although the server has been modified to provide additional information required by this feature), and not on the server, so even if the NCS/Logger sets the ignore it will only be honored by those running 3.1.5 or later (so if you want to have the ability to not be bothered by someone being obnoxious you'll need to upgrade to 3.1.5 or later). The version that is being used by the person you wish to ignore is not important, i.e. you can ignore someone running earlier versions of NetLogger, including NL2.4.

    If an AIM group ignore is sent it will also apply to anyone joining the net afterwards (all group ignore messages are stored on the server and will be processed by a new client when they join the net). NCS/Logger's should never send the request a second time, since that will have the effect of undoing any unignore's done by individual personal preference.

    When an individual does an ignore, the Monitors table entry will immediately turn red. If an NCS/Logger sends a group ignore the related entry won't turn red for themselves until the message has been received back from the server, which won't occur until the next poll, which can take up to 20 seconds. This helps verify that the message was successfully sent out.

    Finally, note that the person being ignored gets no indication that they are being ignored. An NCS/Logger can choose to inform the user via AIM if they want to. When a group ignore is sent, the Monitors entry for the ignored person will not turn red for the ignored person. Even if an NCS/Logger chooses not to inform the user, there's a good chance that another user will notice and comment on it in AIM.

Minor Enhancements

  1. Finished adding help page documentation for the new features added in the 3.1 release, including features just added in 3.1.5.

  2. Modified the layout of the Preferences dialog to put preference items in two columns, since the dialog was getting too long.

  3. Added some clarifying text to the Start Logging net password dialog to reduce confusion.

  4. Made a change to the Monitors window, where the row number will be red for the current user, which will help a user quickly identify which row in the Monitors window is their own.

  5. Made a change to the Load Checkins feature when viewing previous nets. Now, if the associated main window is in STANDALONE mode, in addition to the checkins being loaded into the main window Check-Ins table, the associated net information will be loaded into the net status and control section at the top of the main window.

Bug Fixes

  1. Fixed multiple bugs related to the Preferred Name field. 1) The Preferred Name value was not showing up when a user initially subscribed. It would only appear if a subsequent change was made to that row. 2) The profile change indicator was not changed if the Preferred Name field was updated. and 3) The Preferred Name field was not written to the profile file if an update was done.

  2. Fixed a bug affecting dates in the year 2001, which were converted incorrectly by NetLogger. Currently there is no easy way of fixing existing data other than reimporting from a backup made by a version prior to 3.1.

  3. Fixed a bug where auto saved check-ins files were not being saved in the CheckIns subdirectory.

  4. Fixed an ADIF import bug where bad state values could lead to a crash.

Version 3.1.4 - June 7, 2016


This release is primarily a bug fix release.

Minor Enhancements

  1. Made a change to not export an ADIF tag when there is no associated data (previously NetLogger would export a tag with a data length of zero). This has the desirable effect of making ADIF exports and the Contacts database smaller (as much as 50% smaller). It also provides a workaround for a bug in the Ham Radio Deluxe logger which doesn't handle zero length tags properly (i.e. ADIF data exported from NetLogger and imported into HRD was causing HRD to have problems with the new RX Freq field).

Bug Fixes

  1. Fixed a problem with Auto Save Check-ins where a net name with certain special characters could cause the save of the Check-ins file to fail, since the file name included the net name. Code was changed to change non alphanumeric (except +,- and _) characters to dashes.

  2. Fixed two bugs related to deleting Station Locations which could lead to a crash or a hang.

  3. Fixed a problem with smaller resolution displays where the enable/disable columns dialogs were too long and were partially not accessible. Changed to display the checkboxes and labels in three columns rather than one.

  4. Fixed a problem with importing contacts from the N7XG Logger where the Sent Conf By and Rcvd Conf By fields weren't being set properly. Also added some club/user defined mappings.

Version 3.1.3 - May 25, 2016

New Features

  1. Added support for a new Preferred Name field in the Check-ins table. This is intended as a standard way of setting the name a person prefers to be called by, rather than their formal/legal name that may be reported by the FCC or a QRZ lookup. Some clubs already support this, but they each do it in a different way (storing in the Remarks field, or only storing the first name in the Name field, etc.).

    This field is also supported as an additional field in the Club Profile file, the contacts table, saved check-ins file, etc. Also, a QRZ lookup will fill this field with the persons first name rather than the previous non-standard behavior of filling the Remarks field with the first name. Note there is no requirement that clubs change to use this field, and people are free to hide this column if they don't want to use it.

  2. Added support for the View Previous Nets feature from NetLogger 2.4. This feature has been enhanced to store more information about the net, including the check-ins list state at the time the net was closed. It is now possible to load check-ins from a previous net into the Check-ins table. This may be useful as a last resort backup when a net is closed by mistake (although in most cases this shouldn't be necessary since the check-ins list would still be present in the check-ins table when the net was closed).

  3. The way QSL sent and received status is handled has been changed. The QSL Sent and QSL Rcvd columns have been replaced by the Sent Conf By and Rcvd Conf By columns in the Contacts table. These new columns use letter codes to represent whether a QSL has been sent or received, with different letters representing different delivery methods. Currently a 'C' is used to indicate a QSL card was sent (or received), a 'E' is used for eQSL, and an 'L' is used for LoTW. A 'u' is used in the Sent Conf By field to indicate a contact that has been uploaded to the LoTW server, but which has not been confirmed yet as having been processed by the LoTW server. When the contact has been confirmed as received the 'u' will be replaced by an 'L'.

    Other letters can be used for manually keeping track of QSL status, according to the users wishes. The NetLogger author would like to reserve the use of 'Q' and 'B' for now. Stay tuned for other possible reserved letters. It might be best to use lower case letters, other than 'u', for personal use.

    Previous values in the QSL Sent and QSL Rcvd columns have been mapped to this new format. It is assumed that those columns were meant to represent sending real cards, and a 'Y' in one of those columns will have been mapped to a 'C' in the new corresponding column. Any value other than 'Y' will be interpreted as a card not having been sent or received, which will result in a 'C' not being placed in the new corresponding columns.

    When exporting contacts in ADIF format, the Sent Conf By and Rcvd Conf By fields will be exported using application specific ADIF tags. NetLogger will also export the standard QSL_SENT, QSL_RCVD, EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSL_SENT and LOTW_QSL_RCVD ADIF tags based on information recorded in the Sent Conf By and Rcvd Conf By fields.

    When importing logs in ADIF format, the values contained in the standard QSL_SENT, QSL_RCVD, EQSL_QSL_SENT, EQSL_QSL_RCVD, LOTW_QSL_SENT and LOTW_QSL_RCVD ADIF tags will be ignored if the application specific ADIF tags for Sent Conf By and Rcvd Conf By are also present. If those application specific tags are not present, the values for the Sent Conf By and Rcvd Conf By fields will be constructed from the values found in the various standard ADIF tags previously listed.

  4. Added preliminary support for uploading contacts to Log of the World (LoTW). Currently, in order to use this feature you must already have installed TrustedQSL (TQSL) and use that to export your existing LoTW certificate(s) in PKCS12 format so that they can be imported into NetLogger.

    If you are not already using LoTW you may want to wait for a future release of NetLogger. The plan is to have NetLogger directly support requesting a LoTW certificate from the ARRL, and also have the required support for setting the certificate up. It is also planned that in a future release NetLogger will be able to automatically import all valid LoTW certificates directly from a TQSL installation by either finding the location of the TQSL installation via the Windows Registry, or by telling NetLogger where TQSL is installed (bypassing the need to export certificates from TQSL and then import them into NetLogger).

  5. Added support for creating Station Locations. A station location is a group of attributes associated with your current location, which will be added to your log when you log a contact. For example, this allows you to setup a station location for your fixed home location, and perhaps another station location for a portable location when you are operating in the field, a club location, or perhaps while operating at a friend or relative's home. This information can then be used when sending QSL cards, uploading QSL's to eQSL or LoTW, etc.

    As part of this feature, 20 new fields were added to the Contacts table. These fields correspond to parameters that can be set in the station location dialog, most of which map to standard ADIF fields that can be exported for each contact (some fields are specific to NetLogger). Remember that you can enable/disable any fields that you don't care about. Also, you don't need to fill out every field in the station location dialog. The only mandatory field is the station callsign. Other fields are mandatory when logging contacts that you intend to upload to LoTW. When you first start up NetLogger 3.1.3, a default station location will be created for you. Note that you must always have one station location configured, i.e. you can't delete the last station (but you can modify it).

    Another part of the Station Location feature is that you can specify a club and/or an "alternate" call sign that is currently associated with the station. If you enable this then every time you click the Log Contact button you will log a contact for both your own call sign and another for the club call sign. Note that your callsign will be set for the Operator field for both contacts that are logged. The new Station field will be set with the appropriate call sign, i.e. one of the logged contacts will have the Station field set to your callsign, and the other logged contact will have the Station field set to the club call sign you enabled.

  6. Added support for importing TQSL station location information. Note, there is no support for automatic direct TQSL certificate importation, so TQSL certificates should be imported manually prior to using the TQSL station importation feature, otherwise the imported station locations will not be associated with a certificate and can not be used for LoTW without manually fixing each station location.

  7. Added support for checking with the LoTW server to verify that uploaded contacts (QSO's) have been processed, and to also check whether uploaded contacts have been confirmed by the contacted station (creating a QSL).

  8. Added support for checking with the eQSL server to check for confirmations of eQSL contacts. Also, on the first update NetLogger will also download your eQSL outbox (i.e. all the contacts you've ever uploaded to the eQSL server), so that it can mark any matching contacts in the Contacts table as having been sent (placing an 'E' in the Sent Conf By field).

  9. Added support to allow a club to specify all the parameters related to a clubs standard nets in their Club Information file. This allows a person to configure which clubs they are an NCS/Logger for, which will then add those nets to the Net Name drop down box in the Create Net dialog. Standard nets will be colored blue, to differentiate them from personally created nets using the My Nets feature. Note that any standard net name will cover/hide a corresponding personal net that used the same net name.

    Note that an NCS can specify a password in the Setup/Club Nets dialog for each club. That password will be used when creating a club net. However, the NCS field will remain blank and will need to be manually entered each time. This feature also allows the club to specify the default server that they would like the net to be created on. This feature should reduce the number of mistakes that are made when creating club nets.

    Note that a club administrator (the person responsible for maintaining the clubs Club Information file) must enable this feature before it will be available to use by the club's NCS/Loggers.

  10. Added support to allow the location of the Contacts Backup directory to be configured. Note that previously the Contacts Backup files were ones that were rotated from the Contacts Backup adif file, i.e. they were not the current information at the time of the backup, but two generations removed from that. Now a new backup file is created that is a copy of the current contacts file. This allows the Contacts Backup directory to be located on a different file system (e.g. a network share, a flash drive, etc.).

Minor Enhancements

  1. Upgraded NetLogger from Qt version 5.4.0 to Qt version 5.5.1.

  2. Changed the way contacts are uploaded to the eQSL server. For some this may be perceived as a regression, because when you select multiple contacts to upload, each contact will be uploaded individually to the eQSL server. This may cause the time it takes to upload the contacts to significantly increase, depending on how busy the eQSL server is at the time you do the upload (the time difference is negligible when a small number of contacts are being uploaded and the eQSL server is not very busy).

    This change was made due to the fact that if there was any type of failure during the upload it was difficult to determine which contact(s) had the problem when they were all uploaded together. With them being uploaded one at a time NetLogger can determine when each contact is successfully uploaded, so it can mark them as sent in the Sent Conf By field, and also it can provide better information about which contacts failed to upload.

    Another small advantage of this change is that there is now no limit on the number of contacts that can be selected for upload, and NetLogger now provides a progress bar showing the upload status as it progresses.

  3. Due to the addition of LoTW support, a new eLogs top level menu was created, and all eQSL and LoTW menu items were moved and/or added to that top level menu.

  4. Added support for updating contact fields when checking LoTW or eQSL status. Fields are only updated from the QSL'ing station data if the field was empty or in the case of the grid square, the grid square may be updated to a 6 character grid if the previous data was a 4 character grid and those characters matched the first 4 characters of the received grid square.

    For eQSL the potentially updated fields are RST Rcvd and Grid Square. For LoTW the potentially updated fields are DXCC, Country, CQ Zone, ITU Zone, IOTA, Grid Square, State and County.

  5. Added a new Set Station Info from Current Station tool under the Edit/Modify Selected Contacts menu item that allows setting of the new Contacts fields based on the current station. Note this replaces station location information for the selected contacts with the station location information of the current Station Location. This tool should be used with extreme caution. This feature is primarily for setting these fields for pre-existing contacts. For example, it will be necessary to use this feature if you plan to use NetLogger to upload previous contacts to LoTW.

  6. Added some initial documentation for some of the new features introduced in this release. The documentation is not complete and will be enhanced in a future release.

Bug Fixes

  1. Significantly reduced the chance of a race condition when choosing a net to monitor at the same time the number of nets changed. Also removed the possibility that due to this race condition, a net that is already being monitored could be monitored a second time (which led to crashes).

  2. Made a change to update the contact filters when data for a contact is changed.

  3. Made a change to normalize illegal call sign data when importing ADIF and CSV files.

  4. Made some changes when editing entries in the Contacts table so that when tabbing to the next column you won't get stuck in the State field or any of the multi-line fields. Also tab will skip over non-editable fields (currently only the Cert Name field is non-editable).

Version 3.1.2 - May 24. 2016

Closed beta test version for the 3.1.3 release.

Version 3.1.1 - May 19. 2016

Closed beta test version for the 3.1.3 release.

Version 3.1.0 - May 4. 2016

Closed beta test version for the 3.1.3 release.

Version 3.0.3 - February 5, 2016, Declared STABLE February 12, 2016


This release helps address a resource issue caused by polling of the various Netlogger servers. It would be appreciated if people would update to this release, especially if you are in the habit of leaving the Nets In Progress window up for extended periods of time (it would still be helpful even if you don't do this).

New Features

  1. Since the Nets in Progress window was being changed as part of the modifications to reduce server polling, a new Server Status feature was added at the same time. The Nets in Progress window now lists all the servers that are available, and shows their current status (with a small "led like" indicator. Note that if a known server doesn't show at all, it is an indication that the server isn't currently available. Before a server can be shown, a "Server Info" request must succeed, since things like the server name and other server related parameters are not hardwired into NetLogger, and therefore must be obtained from the server itself before it can be listed. NetLogger will continue to poll the server, and if it eventually responds it will be added to the list of servers. Once a server is listed it won't disappear from the list (but its status indicator may change to red).

    The advantage of this feature is that prior to this release, if no nets were displayed in the table, you couldn't be sure if there was a problem with one or more servers (or your ISP), or there really were no nets in progress. Now, if a server shows a green light next to its name then you know that any nets in progress on that server will be listed in the Nets In Progress table.

Minor Enhancements

  1. Made a change to the way that polling is handled while the Nets In Progress window is up. Now it will start at the default 20 seconds, but will start to degrade over time. The assumption is that the longer the window is up, the less likely a user is actively watching the window and therefore can tolerate less frequent polling. A new slider has been added to the bottom of the window that graphically shows the polling time, and which moves automatically as the polling time increases. A user is free to move the slider back to the left to improve the polling frequency if desired. Even in this case it would be appreciated if a polling frequency of more than 20 seconds was chosen. Note that the window has to be open for more than four hours before the maximum polling frequency of 10 minutes is reached.

  2. Removed support for the WEB column in the View Monitors window, since the web version is no longer available.

  3. Made a change to enable numeric sorting for the Band column.

  4. Added support for a Museum Ship award status.

  5. Changed the Check-ins table context menu entry for Set/Clear Worked Status (and the F3 hot key) to be a Set/Clear Manual Worked Status. Due to changes in 3.0.1 that made worked status more dynamic, the ability to manually set the worked status for a station was not preserved. In order to allow for that, a new manual worked (W) status has been added, which will be persistent until cleared manually. Note that both (W) and (w) status might be set for a station. The (w) status value is now only set/cleared via the Worked Station Flag criteria.

  6. Added support for System Messages checking to be redirected to a "master" server, depending on server configuration. For example, this allows system messages to be retrieved from the NETLOGGER server when logging or monitoring a net on the NETLOGGER2 or NETLOGGER3 server.

  7. Modified the check for latest version algorithm to not inform the user about a new version if the user is already running the new (or later) version.

Bug Fixes

  1. Fixed a bug where if a logger set the state of a station in the Check-ins table to checked-out (c/o), the M/P status and Awards status would be cleared.

  2. Fixed a bug that could cause a crash if a user attempted to import new contacts while an edit was still pending in the Contacts table.

  3. Made another change similar to the change made in 3.0.0 that will help track down a crash that may have been reduced due to the previous change, but is still happening.

  4. Removed some polling that was happening too often, e.g. the checks for a new version, and rechecking of server information.

  5. Fixed a bug when importing a CSV file from the N7XG logger where the sent and received signal reports were swapped.

  6. A few people have reported that their virus scanners triggered on qsvgicon.dll, which is a Qt plugin for scalable vector graphics icons. Although this is a false positive detection, I checked to see if I could avoid shipping that file, since NetLogger doesn't use scalable icons, and I currently don't have any plans to do so. It appears to be safe to remove, so 3.0.2 no longer contains qsvgicon.dll, qsvg.dll and QtSvg.dll.

Version 3.0.2 - February 2, 2016

Closed beta test version for the 3.0.3 release.

Version 3.0.1 - January 11, 2016


This release is to fix a new crash and a few other tweaks that were asked for in relation to new features. Please read the 3.0.0 release notes for the more significant changes.

Minor Enhancements

  1. Modified the Worked Station Flag support to recheck after a change in State or M/P status for a Check-in, due to those being possible criteria for Worked Station Flag matching.

  2. Sanitize Band values that are not supported by ADIF when exporting ADIF (to a file or eQSL), but still support the non-standard values within NetLogger by adding an Application specific ADIF tag for storing the unsanitized version of the band.

Bug Fixes

  1. Fixed a crash that happens when Auto Save Checkins was enabled, that was introduced when changing the naming format of the default checkins file.

  2. Fixed a typo that was preventing the processing of the FR:POL award status when being read from a club profile file.

Version 3.0.0 - January 10, 2016


Although the release number has been set to 3.0.0, that doesn't mean this release is automatically a "stable" version. This release is a candidate to be a "stable" version, and will only be declared stable after it has been released for a while and is shown to be relatively stable. If there are any significant problems found in this release there will be follow-on 3.0.x releases. However, the next release with new features (other than minor tweaks and bug fixes) will be a 3.1.x release.

New Features

  1. Implemented a new M/P column in both the Check-ins table and the Contacts table. This column is for specifying Mobile or Portable operation status (vs. fixed status). There are three ways of entering this status during check-ins. One way is to use the context menu (right mouse click) and choose either Mobile or Portable status. This will show up as either a M or a P in the M/P column.

    The second way for entering Mobile/Portable status is to just add a /M or /P when entering the callsign. The /M or /P will be removed and the corresponding value will be set in the M/P column. Finally, you can just type M or P in the M/P column. You can also type lower-case m or p, and they will be entered as upper-case.

    The M/P column is enabled by default, and will be placed as the second column. However, both of these defaults can be changed.

    NOTE: The SATERN server does support transporting this status, but it will cause interference with the status colors of NL2.4 clients.

  2. Implemented a new Award Info column in both the Check-ins table and the Contacts table. This column is for setting various attributes that clubs care about for various club awards, but in a club independent fashion. This feature may not be instantly useful, especially if a club already uses another field for this purpose, but it is an enablement step for future features (and they can already be used in forming a default qsl message). These status values are set using the context menu. There is a new "Club Award Status" submenu where all the new values can be set.

    Some of the more static award status values can also be set directly from a new field in the Club Profile (.prf) file.

  3. Implemented a new Club column in the Contacts table. This field will be set with a short club code (currently the same as the clubs Profile name) when you log a contact during a net using the Log Contact button. This is useful in conjunction with the new Worked Station Flag features, allowing you to match on a club rather than a net.

  4. Changed the way that the Worked Station Flag is set, and added a variety of new criteria that can be used for setting the worked (w) status for entries in the Check-ins table. The old value, from 2.9.16 or earlier will automatically be converted to the new format when you first install and run 3.0.0.

    Clicking on the Worked Station Flag menu item under the Setup menu will now bring up a dialog with checkboxes to enable or disable various matching criteria for setting the worked status for entries in the Check-ins table. Note that the Call Sign is always included in the match. See the Flagging Worked Stations help page for more details.

  5. Implemented a new Modify Selected Contacts feature. Actually, this is the beginning step in implementing various tools for making modifications to your Contacts database. Currently two new tools have been implemented (they can be found under the Modify Selected Contacts menu item, which is in the Edit menu. All of the tools require that you first select a set of contacts to operate on. In many cases, using the various Contacts filters can increase the usefulness of these tools. The Custom Contacts filter will be especially useful in this case.

    The first tool is the Replace Field tool. This will bring up a simple dialog that shows you how many contacts have been selected, and lets you choose a field for replacement. There's also a value box where you can enter a value that will replace the contents of the selected field in every selected contact. The field will be cleared in each selected contact if you leave the value box empty. This is a powerful, but also dangerous tool. Please read the "How to Modify Multiple Contacts" help page for more details and warnings.

    The second tool is the Set Club from Net Name tool. This is a specialized tool whose sole purpose it to set the new Club column based on the contents of the Net Name column. This tool will use each net name and compare it to the known list of "legal" net names specified by each club. If a match is found the associated club code will be placed in the new Club column. This feature only works for net names that perfectly match. So some manual fixup may still be required afterwards. Note that this tool will only place a value in the Club field if it is currently empty. The Replace Field tool could be used to clear the Club field if the field contains incorrect values.

    The Replace Field tool might be useful in manual fixup of the Club field. For example you could use the Custom Contacts Filter to choose all contacts whose net name had a certain word or part of a club name in it. You could then select all those contacts and use the Replace Field tool to replace the club field with the appropriate value.

Minor Enhancements

  1. The call sign validation code for the operator value has been fixed to better conform to the world wide callsign rules. Previously NetLogger was not allowing the 2x4 callsign format used by Australia for Foundation class licensees.

  2. Added a Donate menu item that simply brings up the Donate help page, which provides more details about helping support the various NetLogger servers.

  3. Support has been added for new NetLogger servers. Note that only NCS/Loggers have to be concerned about this when they are creating a net, since they are the ones who choose which server to create a net on. NetLogger polls all of the servers it knows about at the same time and lists the full set of nets running on each of the servers, so those wanting to join a particular net don't need to concern themselves with which server it is running on. Additional servers were added primarily for load balancing, but it also increases robustness, since in the case where one server is not available there will be other servers that will (hopefully) still be available for use.

    The general rule of thumb for choosing a server will be that clubs (or individuals) who run only one net per day should stay on the NETLOGGER server by default. Clubs that have more than one net per day will be assigned a default server to use. Please consult with your club NCS coordinator if you are not sure which server to use. These assignments may not roll out until after 3.0.0 is released. Note that NL2.4 users will have to manually program the new servers into their configuration, and will have to select one server at a time to look for nets. That's why it makes sense for clubs to stay with one particular assigned server, so that NL2.4 users will know where to look.

  4. The default QSL Message feature has been enhanced to allow "variables" to be added to the message, whose value will be substituted into the message for a particular contact when it is logged with the Log Contact button. The variable names have a dollar sign ($) before and after the name. Also, if you place a plus sign (+) between the dollar sign and the start of the variable name, a space will automatically be added after the end of the substituted value, as long as the substituted value was not empty. See the Using a Default QSL Message help page for examples of how to use a QSL Message Variable, and the Default QSL Message Variables help page for a list of the supported QSL message variables.

  5. NetLogger 3.0.0 has been changed to use the standard ADIF QSLMSG tag, rather than the non-standard QSL_COMMENT field that was used previously (and which NL2.4 generates). NetLogger will still import the QSL_COMMENT tag for ADIF format imports, but it will only use the QSLMSG tag for exporting that data when exporting in ADIF format.

  6. The default file name for saving check-ins and for auto saving check-ins has been changed to add the hour and minute (in addition to the month day and year).

  7. Finished the planned html based documentation for the 3.0 release. I may add further documentation in a later release, along with documenting any new features added. But the documentation for this release is considered "complete". I plan to stop distributing the NL 2.4 to 3.0 pdf file document at some point in the future.

Bug Fixes

  1. Fixed a crash that could happen when sorting by certain columns in the Contacts table.

  2. Fixed a few single or rare occurrence crashes.

  3. Made some changes that might fix the most common crash still seen in version 2.9.16. I haven't been able to find the root cause of the problem, but it might actually be a Qt bug. I changed the way viewing monitors is handled to avoid using the suspect Qt api. We'll see if this problem goes away in 3.0.0.

Version 2.9.16 - September 4, 2015

Bug Fixes

  1. Fixed a bug that was introduced with the Country column support, which could cause a crash when editing your contacts.

Version 2.9.15 - September 2, 2015

New Features

  1. Implemented a new Country column in both the Checkins table and the Contacts table. This column can only be set (for sending to the server) by a logger using version 2.9.15 or later. The data will only be seen by people monitoring the net with version 2.9.15 or later. You will need to enable the Country column via the Enable/Disable columns submenu under each table in the Edit menu. Also, don't forget you can rearrange the order of columns (by default the Country column is the last column).

    The country data will be copied to the contacts section when logging a contact. Country data will be exported using the standard ADIF tag when exporting contacts in ADIF format. Country data will not be exported when exporting contacts in CSV format. Country data will automatically be filled in during a QRZ lookup, if enabled.

    Although the DXCC field already existed, previously it was a local only field. Now it also can be set by the logger and transmitted to all monitors.

    Both the DXCC field and Country field are supported in the prf file in a backwards compatible way. The two fields can be added to the end of the line (DXCC first, Country after that). NL2.9.14 and earlier (including NL2.4) will ignore the extra fields (and will remove them if you update the profile file from within an earlier version of NetLogger).

    When doing a profile update, the new version will only add the extra arguments if you check either the DXCC or Country checkbox in the Club Profile Update Fields dialog under the Setup menu. The extra fields will also be preserved and rewritten if the original profile file that was loaded already contained the extra fields.

    NOTE: The SATERN server doesn't support sending these fields.

Minor Enhancements

  1. Automatic scaling support for some previously fixed size widgets has been added (Windows only, MacOS already handles scaling in a better fashion), in order to better support high DPI screen displays. This will be particularly noticeable for those running at 150% or greater font scaling. Note that default values for font sizes, column widths, font height margins, etc., will likely be incorrect for high DPI screens; but those values can be adjusted by the user.

  2. Implemented View / Color Legend by simply opening the Check-In table grid colors help page.

  3. Change the default Date/Time to be the current UTC time when inserting/adding a new (empty) contact in the Contacts table.

  4. Added support for a Help Index.

  5. Made the Help dialog non-modal so you can read the help documentation while still performing other functions.

  6. Added a significant amount of help page documentation. This is about 70% complete. Finishing this documentation is the primary blocker for creating the 3.0 release.

  7. Changed sorting for the frequency and DXCC columns so that they are sorted numerically rather than alphabetically (e.g. 7.190 will come before 14.290 now).

  8. Made a change to the insert functionality in the Contacts table. When the insert button is clicked (the one with the plus sign icon), the cursor will be placed in the call sign field of the new line, and edit mode will be entered.

  9. Adjusted the AIM URL detection heuristic to reduce false positives when creating hot links.

  10. Added support for checking for a new stable or beta version of NetLogger. You can turn this off in the preferences dialog in the New Version section.

  11. NetLogger now sends a blank space rather than an empty string when creating a net without specifying an NCS. This mimics NL2.4 behavior, and the SATERN server doesn't allow an empty string for NCS.

Bug Fixes

  1. Changed the closing sequence to prevent crashes under some circumstances when multiple Net windows were used.

  2. Fixed a bug in instant message parsing that could lead to crashes, including crashing other users when they read certain instant messages.

  3. Fixed another bug in instant message parsing related to bbcode which could cause spurious characters, or characters from the previous message, to be included in a message with badly formatted bbcode.

  4. Applied a patch from the Qt team that fixes a bug that was causing NetLogger to occasionally crash when it was first started.

  5. Fixed a problem on Windows where in some cases crashes weren't being detected and therefore a crash dump was not created for uploading.

  6. Fixed a bug where Relay status (rel) couldn't be set in combination with some other statuses that should be allowed.

  7. Fixed a bug that could lead to a crash if an attempt is made to log a contact where the callsign was illegal.

Version 2.9.14 - May 5, 2015

New Features

  1. Added a Profile Change Indicator feature where the row number in the checkin table changes to red if a change is made in that row that is one of the enabled fields in the Setup/Profile Update Fields dialog, and there is data in the callsign field. This is useful to show which lines might be candidates to do a Add/Update Club Info on (which will change the row number back to black).

    The row number will also turn to red when a new callsign is entered and the profile lookup fails.

    This row indicator can be disabled via the Enable Profile Change Indicator checkbox in the Appearance section of the Edit/Prefences dialog.

  2. Added a Sync Checkin Table to Profile feature that does a Add/Update Club Info for each entry in the checkin table whose profile change indicator (see above new feature) is set.

  3. Added the Upload Latest Club Profile feature from NL2.4 to the Function menu. This works similar to the way it works in NL2.4, except the ftp connection will be done using Passive mode, rather than Active mode. Passive mode is more likely to work through various home routers/firewalls, and most default ftp server configurations support it. However, it is possible that some firewall settings may need to be changed on the ftp server to enable passive mode (not likely).

  4. Added the support for a OS independent Help system in NetLogger, using Qt's rich text engine (a text oriented HTML 4.01 subset). NOTE: There is no content yet, other than the Donate (for server maintenance) help page. That's not a hint, I simply wanted to write a page that tested external http links. But that doesn't mean it's not a good idea. :)

    The support involves a minimal text browser window in NetLogger (Help/Contents), plus new tools for me to maintain the installer database for all the new help files, plus tools to generate help pages with consistent styles via templates, and to auto-generate the contents page.

Minor Enhancements

  1. Allow a 3 letter prefix in the callsign (used by some SWL callsigns).

  2. Changed the "Stop Logging" and "Stop Monitoring" semantics so that a net creator will still be prompted to close the net when leaving the net. This helps ensure that if the net is left open it is done intentionally (i.e. someone else has taken over logging or the logger intends to return, etc.). This should reduce the number of orphan nets.

  3. Allow local control of Net Name, Frequency, Mode and Band while monitoring, even if the logger is using the new version of NetLogger. There are still valid reasons for local changes, even if the logger can now also make changes that affect everyone. So now both have "shared" control, i.e. you can make a local change and it will stay in effect unless the logger subsequently changes it. This seemed like the best compromise without having to add extra controls like local locking, etc. (NOTE: The logger does not have control of these fields when using the SATERN server).

  4. Added an "Unhide" button to the "View Directories" dialog. This button is only available in the Windows version of NetLogger. It unhides any hidden directories in the Config Directory path, enabling easy navigation to the Config Directory via Windows Explorer. This is helpful due to the fact that Microsoft Windows sometimes hides the users "AppData" directory by default.

  5. Added a "Release Notes" menu item under the Help menu, which uses the Qt rich text engine to display the release notes within the program. You may be using that feature to read this right now.

  6. Added a checkbox in the Contacts section of the Preferences dialog that allows the choice of exporting the Member Id value in the ADIF Comment field, surrounded by # characters.

  7. Added an "Online Users" count at the top of the Monitors window.

  8. Added ClubInfoList entries for GOBG (Good Ole Boys Group), Moonlighters and SVARA.

Bug Fixes

  1. Properly escape passwords for QRZ and eQSL so that html "unsafe" characters can be used in the password.

  2. Fix some issues that could cause a crash on exit.

  3. Fixed a bug where if there was a failure in downloading a prf file you wouldn't be able to download it again (only affected profiles in the club info list).

  4. Fixed a problem when changing date/time in Contacts table so that the contact is moved as a result. This could cause a crash in some cases if any filters were enabled.

  5. Commit any pending edit in the Contacts table when exiting NetLogger.

  6. Make sure AIM window starts with scrollbar at bottom so that auto scrolling happens by default initially.

  7. Fixed a bug where if you did a clear row on a row that was empty, a lock wasn't properly released. This could lead to a "lock held" crash later on.

Version 2.9.13 - April 17, 2015

Initial public beta release.