View Issue Details

IDProjectCategoryView StatusLast Update
00030013 - Current Dev ListBugpublic2019-04-08 11:22
ReporterWA9PIEAssigned ToWA9PIE 
PrioritynormalSeverityminorReproducibilityalways
Status acknowledgedResolutionopen 
Product Version6.5.0.157 
Target VersionFixed in Version 
Summary0003001: Callsign lookup function does not appear to be working as designed
DescriptionWe have a user who reports that fields for new log entries for calls that are already in their log are not filled from the Logbook (Logbook being selected as an "Enabled Method" in the Callsign Lookup dialog box.
Steps To Reproduce- make sure that the only Enabled Methods in the Callsign Lookup dialog box are Logbook and Country List (and in that order)
- open the ALE and put a call in the callsign field
- invoke the callsign lookup function with either tab or pushing the "Lookup" button (this won't do much because the enabled methods won't turn up anything)
- populate a good number of the fields in the QSO record; save that record

Then create another log entry:
- open the ALE and put a call in the callsign field
- invoke the callsign lookup function with either tab or pushing the "Lookup" button (this won't do much because the enabled methods won't turn up anything)
- notice that none of the fields are filled by the Enabled Method (the Logbook)
Additional InformationThe attached document describes the intended design of the Callsign Lookup function wherever it is used.
TagsNo tags attached.
ModuleLogbook
Sub-ModuleCall lookup
TestingNot Started

Relationships

related to 0003125 acknowledgedWA9PIE 3 - Current Dev List QSOs with stations that aren't in a valid DXCC country show up in the awards totals for a country and should not 
related to 0003015 closedK7ZCZ Ham Radio Deluxe Logobook ALE lookup code is overrun by copy-and-paste 
related to 0003047 closedK7ZCZ Ham Radio Deluxe move "Test" feature of Logbook's Callsign Lookup config to its own property page 
related to 0003046 closedK7ZCZ Ham Radio Deluxe move controls for the config of each Logbook Callsign Lookup data source their own property page 
related to 0003049 closedK7ZCZ Ham Radio Deluxe V6.4.0.907 - ALE showing Double City in fields 
related to 0003130 closedPD9FER 4 - Closed w/o Action Logbook ALE lookup disregards position set in Callsign Lookup order 
related to 0003135 closedK7ZCZ Ham Radio Deluxe Logbook's MessageDate() function isn't useful 
related to 0003145 closedK7ZCZ Ham Radio Deluxe Enhance logging output of callsign lookup feature 
related to 0003147 closedK7ZCZ Ham Radio Deluxe Logbook callsign lookup data source doesn't return much data 
related to 0002262 acknowledgedWA9PIE 3 - Current Dev List Add bulk callsign lookup in Logbook 
related to 0003196 acknowledgedK7ZCZ 3 - Current Dev List Logbook QTH Column Issue 
related to 0001395 acknowledged 1 - Backlog Automatically calculate location 
related to 0003192 acknowledgedWA9PIE 3 - Current Dev List Lat/Long, direction, and distance are incorrect in the Logbook ALE; "Log Coordinates" has opposite affect 
related to 0003187 acknowledgedWA9PIE 1 - Backlog V6.5.0.187 to 6.5.0.190 has problems with the Callsign Lookup Pane in the Logbook. 
related to 0001660 acknowledgedWA9PIE 2 - Next Dev List (Holding Area) Use Maidenhead locator (grid square) for ALE coordinates 
related to 0000472 acknowledgedWA9PIE 2 - Next Dev List (Holding Area) Add QRZ.com photo download into contact & option to show on ALE 
related to 0002006 acknowledgedWA9PIE 1 - Backlog Unify ALE into a single window for Logbook and DM780. Add a pictorial compact QRZ page within the larger unified ALE window 
related to 0001554 acknowledged 1 - Backlog Add function to use Callsign lookup on log import or initiate full log update 
related to 0002883 new 1 - Backlog Calbook (qrz.com) should not override UDP API supplied value for grid 
related to 0003284 resolvedK7ZCZ 3 - Current Dev List remove support for QRZ CD lookup 

Activities

WA9PIE

2018-12-18 11:52

administrator  

Callsign Lookup.docx (281,495 bytes)

K7ZCZ

2018-12-18 15:23

manager   ~0006703

Is this issue about fixing the specific problem that customer reports, or is it about implementing the attached specification in its entirety?

WA9PIE

2018-12-20 12:05

administrator   ~0006735

In answer to your question...

I'm not sure if it's possible to fix the specific problem the customer reported without checking the whole entire callsign lookup function. If I were able to read the code, I suppose I'd know whether it's the entire callsign lookup function that wasn't done correctly... or if it's just this one lookup method.

At some point, we do need to finish it to its intended design. I would look for guidance from a developer who has looked at the code.

I'm going to run through some additional tests with other lookup sources and see how that goes.

K7ZCZ

2018-12-27 18:32

manager   ~0006818

A bit of code cleanup with this checkin:
https://hrdsoftware.visualstudio.com/HRD/_versionControl/changeset/4650

K7ZCZ

2018-12-31 11:30

manager   ~0006829

Mantis 3015 cleans up the ALE lookup implementation significantly. More work to do, but this helps it become approachable.

Issue History

Date Modified Username Field Change
2018-12-18 11:52 WA9PIE New Issue
2018-12-18 11:52 WA9PIE Status new => assigned
2018-12-18 11:52 WA9PIE Assigned To => K7ZCZ
2018-12-18 11:52 WA9PIE File Added: Callsign Lookup.docx
2018-12-18 15:23 K7ZCZ Assigned To K7ZCZ => WA9PIE
2018-12-18 15:23 K7ZCZ Status assigned => feedback
2018-12-18 15:23 K7ZCZ Note Added: 0006703
2018-12-20 12:05 WA9PIE Assigned To WA9PIE => K7ZCZ
2018-12-20 12:05 WA9PIE Steps to Reproduce Updated View Revisions
2018-12-20 12:05 WA9PIE Note Added: 0006735
2018-12-20 15:36 K7ZCZ Assigned To K7ZCZ => WA9PIE
2018-12-20 15:36 K7ZCZ Status feedback => new
2018-12-27 18:32 K7ZCZ Note Added: 0006818
2018-12-31 11:29 K7ZCZ Relationship added related to 0003015
2018-12-31 11:30 K7ZCZ Note Added: 0006829
2019-01-07 11:19 K7ZCZ Relationship added related to 0003047
2019-01-07 11:19 K7ZCZ Relationship added related to 0003046
2019-01-20 11:21 K7ZCZ Relationship added related to 0003049
2019-01-28 14:46 K7ZCZ Relationship added related to 0003130
2019-01-29 10:06 K7ZCZ Relationship added related to 0003135
2019-02-01 09:34 K7ZCZ Relationship added related to 0003145
2019-02-01 15:48 K7ZCZ Relationship added related to 0003147
2019-02-01 18:25 K7ZCZ Relationship added related to 0002262
2019-02-25 18:17 K7ZCZ Relationship added related to 0003196
2019-02-27 19:28 WA9PIE Relationship added related to 0003125
2019-02-28 01:31 WA9PIE Relationship added related to 0001395
2019-02-28 01:33 WA9PIE Relationship added related to 0003192
2019-02-28 16:08 WA9PIE Relationship added related to 0003187
2019-03-02 00:25 WA9PIE Status new => acknowledged
2019-03-02 01:03 WA9PIE Relationship added related to 0001660
2019-03-02 01:22 WA9PIE Relationship added related to 0000472
2019-03-02 01:22 WA9PIE Relationship added related to 0002006
2019-03-02 01:32 WA9PIE Relationship added related to 0001554
2019-03-05 23:41 WA9PIE Relationship added related to 0002883
2019-04-08 11:22 K7ZCZ Relationship added related to 0003284