View Issue Details

IDProjectCategoryView StatusLast Update
00035262 - Next Dev List (Holding Area)Bugpublic2020-07-02 02:20
Reporterg3ucqAssigned To 
Status newResolutionopen 
PlatformPCOSWindowsOS Version10 64 bit Home
Summary0003526: Adding a call sign previously worked error in ALE
DescriptionAdding a callsign that has previously been worked, pressing Partial or Exact does not populate the Logbook tab in ALE.
Only under certain circumstances.
Steps To ReproduceOpen the Logbook and enter a call sign that has previously been worked.
Press the Logbook tab and either the Partial or Exact should be pressed.
Press the Lookup button.
Data is added to the ALE pane but no data shows under the Logbook tab.
Press the 'Find' button.
Previous QSOs will then show under the Logbook tab.
Press the Reset (F4) button to remove all the data.
Now re enter the same call sign as before and press Lookup.
Now press either the Partial or Exact buttons. The Logbook will be populated.
Now press Cancel to close the ALE.
Reopen the ALE and add the same call sign as before.
Press the Lookup button and the ALE pane is populated.
Press either the Partial or Exact buttons again and the Logbook is not populated.

Additional InformationThis shows that the Logbook lookup ONLY works after the Find button is used but not after the Lookup button is used.
Is that the way it should be? I think not.
TagsNo tags attached.
Sub-ModuleALE Window
TestingNot Started



2019-11-02 06:59

updater   ~0009113

Confirm G3UCQ's findings. Populating the Logbook tab with previous QSOs was automatic prior to v6.7, or perhaps the FIND button was persistent once clicked.. Having to click FIND each time a call is entered is very annoying.

Issue History

Date Modified Username Field Change
2019-10-29 08:53 g3ucq New Issue
2019-11-02 06:59 w4elp Note Added: 0009113
2019-11-09 09:06 WA9PIE Project 1 - Backlog => 3 - Current Dev List
2020-07-02 02:20 WA9PIE Project 3 - Current Dev List => 2 - Next Dev List (Holding Area)