Found spot

Lou not sure exactly what you are asking but if you right click on a spot on the pan you can delete it.

Ah ok,

Well I just wrote up a long post on my own logging/control software I've written.  In that I stated that when the spots from Flex were first introduced I thought they had missed the mark.  

The way the spots work they are just a visual display of data you (or some spotting program) sends to the radio.  There is very little intelligence except perhaps to tune the slice to the spot when you click on it.

But after implementing Flex spots in my software I have reversed my thinking that their approach is really quite brilliant.  They are suggesting by their implementation that any logic regarding spots should be in an external program and they've provided all the tools needed to do just that.

A well written external program can receive Flex notifications of spot activity and can also using the Flex API tell the radio to do things when a spot is clicked.

Here is an example of what I've implemented.   If I click on a spot on the pan, my software receives the event from the Flex.  The flex has already tuned the slice to the spot for me.  My software looks at the data in the spot and makes some decisions:

1) Mode to set.  If the spot is up in USB or LSB land I go and set that correct mode

2) Offset - Many spot posters will post something like EA9D Up 2 or something similar.  I look for that data and I actually set my XIT on and up + 2.   So when all is said and done my slice is on the spot, in the correct mode and there is an offset applied (XIT) if one was listed in the spot.

So back to your question... I think Flex would say that an external program should be the thing that searches spots as you suggest.  If written well it could interface with a log and even tune you to spots you need.