Hi again Mike/Graham
As I say, I do appreciate the position. I live just south of Edinburgh Airport, so do get a fair number on the list when testing from home, but haven't found this to be a problem in flight. You need to be aware that the traffic screen is principally provided to allow us to see what is going on in the background under 'relaxed' conditions - not when we should be looking outside for a contact. We wouldn't expect pilots to be swapping back and forward between screens in flight (though we do have to do so quite a bit during testing).The way the system works is that PAW receives and decodes all available traffic signals and uses the traffic screen as a sort of 'holding pen' before filtering them and presenting ADSB and P3i within your selected altitude filter range, together with the 'strongest' / highest risk only of the bearingless Mode C/S contacts to your Nav system. So a fair proportion of the traffic at the bottom of the table is effectively irrelevant as far as the Nav system and pilot is concerned.
Remember also that on this occasion, Lee has released a Beta Development Version early so you can all benefit from Mode C detection while we continue to test and further refine the software. Your comments will of course be taken into account in this development. Meantime, please try not to get too hung up on the traffic table.
Hope this helps relieve your concerns
Regards
Peter