View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003534||3 - Current Dev List||Bug||public||2019-10-30 19:02||2019-10-30 19:23|
|Target Version||Fixed in Version|
|Summary||0003534: Lookup pane spuriously looks up call signs only partially entered|
The call sign lookup pain works on a timer of about half a second and will try to perform a look up operation while the user is still typing. This is a poor user experince as the result is startling and unexpected. The pane populates with incorrect information. As a lookup operation also several seconds to complete, and doesn't show progress, it's not readily corrected.
Generally, a timeout shouldn't be a duration less than the duration of the operation itself.
|Steps To Reproduce|
1) Start up the Logbook. This issue reproduces with either 6.6 or 6.7 builds. Might reproduce with earlier builds, too.
2) Use the "Lookup" command in the "View" menu of the Logbook to show the Lookup pane
3) Enter "N9V". Pause here. Maybe you're trying to remember the call sign of that operator -- was it "N9VG" or "N9VJ"?
BUG#1) Doesn't matter what you wanted; the logbook has already looked up the wrong call sign at N9V.
4) Type "G".
BUG#2) Wait. The first operation isn't complete yet. It will finish after a few seconds, then the "N9VG" operation will start.
|Tags||No tags attached.|
Good point. This is similar to the topic related to partial calls that was changed a couple years ago. It's reasonable to expect the user to hit "Enter" or something in order to let the function know that it was meant to search.
Keep in mind... clicking on a spot from the DX cluster is meant to put the spotted call into the Lookup Pane and do the lookup. We wouldn't want the user to also have to go over there and take additional actions to cause the lookup in the pane (clicking in the field and hitting Enter, for example).
We can do this work post 6.7.