View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003029 | 3 - Current Dev List | Bug | public | 2019-01-03 14:22 | 2019-10-20 17:11 |
Reporter | K7ZCZ | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Summary | 0003029: HRDSync.rtf documentation mentions HB9DRV, is outdated | ||||
Description | The product installs to the "C:\Program Files (x86)\HRD Software LLC\Ham Radio Deluxe" directory a file named "HRDSync.rtf" This file contains mentions of HB9DRV and his website, and has outdated content. It's not clear that the "sync" feature remains viable; perhaps it should be removed from the product, along with the documentation. If the feature remains, it should be cleaned up -- including updating this file for content and correctness. | ||||
Tags | No tags attached. | ||||
Module | Setup | ||||
Sub-Module | (select) | ||||
Testing | Not Started | ||||
related to | 0000520 | acknowledged | 1 - Backlog | HRD Synchronizer does not work |
|
The Synchronizer is a viable utility in HRD. It allows users who have transceivers which have very good transmit qualities but questionable receive quality and has CAT control capabilities to synchronize the TX frequency of their transceiver with a communications receiver, which also is capable of CAT control and has much better receiving quality. Many hams have used the Synchronizer in some very ingenious ways to synchronize two different radios together, so, I would definitely say this is a viable utility. The current issue is that it worked in V5.x, but somewhere along the line the code got changed or corrupted in some way so it doesn't function as it was originally designed. |
|
This issue isn't about rebuilding the Synchronizer feature; it's about the content of this file, specifically. It's easy to place new content into the file, but I'm not the person who should be writing or editing that content because I'm completely unfamiliar with the feature. It's possible that, if the feature changes or is removed, this file should be removed. Looks like Mantis 520 is being used to track the issues with the utility itself. |
|
this was status == assigned, but was assigned to nobody. I'm resetting the status to "new" |
Date Modified | Username | Field | Change |
---|---|---|---|
2019-01-03 14:22 | K7ZCZ | New Issue | |
2019-01-03 23:18 | KB3NPH | Note Added: 0006876 | |
2019-01-03 23:19 | KB3NPH | Assigned To | => K7ZCZ |
2019-01-03 23:19 | KB3NPH | Status | new => assigned |
2019-06-16 11:15 | K7ZCZ | Note Added: 0008096 | |
2019-06-16 11:15 | K7ZCZ | Assigned To | K7ZCZ => |
2019-10-20 16:15 | K7ZCZ | Relationship added | related to 0000520 |
2019-10-20 16:16 | K7ZCZ | Assigned To | => K7ZCZ |
2019-10-20 16:16 | K7ZCZ | Status | assigned => new |
2019-10-20 16:16 | K7ZCZ | Note Added: 0008884 | |
2019-10-20 17:11 | K7ZCZ | Assigned To | K7ZCZ => |