Simon,
Not a lot of info to go on here... As you are the only one reporting this issue and I have never seen it in any of my testing I am not even sure where to be begin looking. Initially in your post you thought it was more wide spread. So what have to done as far as testing to narrow it down the the eSearch? I am definitely willing to debug this if I can duplicate your issue. If you switch your config.xml file and use esri base maps and not Bing do you get the same result? Do you have any slow map services in your map? are all map services using the same projection? Some many variables and questions...
Simon,
Not a lot of info to go on here... As you are the only one reporting this issue and I have never seen it in any of my testing I am not even sure where to be begin looking. Initially in your post you thought it was more wide spread. So what have to done as far as testing to narrow it down the the eSearch? I am definitely willing to debug this if I can duplicate your issue. If you switch your config.xml file and use esri base maps and not Bing do you get the same result? Do you have any slow map services in your map? are all map services using the same projection? Some many variables and questions...
Robert,
As all the others, thank you so much for putting your time into these things. I hate to bring this up but I believe there is a bug in the spatial search. It seems to be stuck on "Intersected by Envelope of" option. After I apply a search distance and generate a buffer I then go to select all polygons that intersect it and it selects the same polygons no matter which option I choose ("entirely contained in", "intersected by" or "intersected by envelope of").
PS. This is with your latest release: 2.2.2
All,
Version 2.2.3 now available.
Version 2.2.3 - 01/06/2011
* Fixed Issue with all spatial button firing intersects instead of what they were intended to fire
* Added a clear text button to the results page.
* Better Spatial Icons