locked Re: Ver 2.50.0 issues


HamApps Support (VK3AMA)
 

On 14/04/2021 10:41 am, Bill Barrett wrote:
Moved over to Multicast and all is well now.

Couple of "Nice to Haves"

1. Filter USA calls only. I run HF - 6M on my 6700 so want to see: Caribbean, Mexico, Canada which are filtered out by the N.A. filter. 
   Filtering out USA calls in the Callsigns window would reduce the number of entries on busy bands like 40 & 20M. 
   Finally, it would be nice if each Callsigns window could have it's own filters.

2. Sort Callsigns window by 1, CQ  2. 73 3. DX 4. all others.

Thanks, could not operate FT8 without this app.

Bill W2PKY

Good stuff!

1. USA only filtering is on the todo list along with every other Country. It's unlikely to happen in the near future however. The same applies for Filtering at the Callsigns window level. Everything displayed in the Callsigns window is still coming from the old JTAlert code and there are issues with trying to implement this currently.

2. Sorting, very unlikely to happen. Sorting by its nature consumes extra CPU resources, depending on the algorithm used adding to a slowdown of the Callsigns display. The biggest problem however is that to sort a list of decodes, by any criteria (frequency, db, message type, country, etc) requires that all the decodes are available prior to sorting which means hanging onto the decodes and waiting till they have all been received and then applying the sort.  That would add seconds to the time to display the Callsigns. With WSJT-X now supporting early decoding and up to 3 passes, holding off the Callsigns display until all have been received is a show-stopper, IMO.

There are alternate solutions to sorting in batches but they will result in a continuous shuffling of the Callsigns in the display as each is received from WSJT-X, with the shuffling ending only after all decodes have been received.


de Laurie VK3AMA



Join Support@HamApps.groups.io to automatically receive all group messages.