+xFeel free to suggest an alternative algorithm that will address the issues raised but will not detract from any existing used search behaviour.
Tim,
I have no idea what lies behind the existing algorithm as my earlier/originating issue still persist.
If I am looking for LUXAL, the outcome is still identical as previously.
What would help me, would be an algorithm with the following approach:
Note that this will primaly/only be relevant during flight.
During flight (Go fly) , 'Direct to' ... : (Maybe discard any match fx > 100nm away.)
Entering L, I would expect any matches complying to L*, including LUXAL, sorted by distance
Entering LU, I would expect any matches complying to LU*, including LUXAL, sorted by distance
... and so on.
Currently LUXAL is *NOT* shown until you make the full spelling, which doesn't make any sence to me ... why isn't LUXAL shown until fully spelled?