Enhanced Search Widget for FlexViewer 2.1

[RobertScheitlin__GISP]

All Here is my next widget in the FlexViewer 2.1 series

Special thanks to Erwan Caradec for contributing to this code.

The Enhanced Search Widget extends the standard search widget with a floating data grid and a new spatial query w/buffering.

http://www.arcgis.com/home/item.html?id=5d4995ccdb99429185dfd8d8fb2a513e

[DavidAllen]

David,

   Nope no tolerance setting for them. As you can see on my preview site there isn't an issue with point or line selection. http://gis.calhouncounty.org/IdentExample/index.html?config=config-eSearch.xml

Are you trying to select points using point or line? if so you are HIGHLY unlikely to click in the precise location to get a result.

Yep - point on point selection. That must be why it's not working. I think I can transfer the point location of headstones to a polygon showing the burial site and then it will work with a point selection.

[RobertScheitlin__GISP]

Jim,

   Currently there is no configuration change to disable those but That would be an easy add for the next release. Currently you would have to comment out these lines:

if (configSearchText.length)
     wTemplate.addTitlebarButton(ICON_URL + "i_searchtext.png", textsearchLabel, showStateTextSearch);

[JimWelsh]

Robert,

Thanks for the info, it was exactly what I was expecting.  The link is removed as I wanted, but the text search still loads by default when the widget is opened.  Where is the best place to change the default search?

Thanks again.

[RobertScheitlin__GISP]

Jim,

Hopefully version 2.2.5 will come out today and it will have all of this configurable.

i.e disablebuttons, defaultselectionoption, toleranceforpointgraphicalselection, text search by selecting from valid domain values in a combobox when this option is set in config.

If you need it fixed right away then the code change would be:

<viewer:BaseWidget xmlns:esri   ="http://www.esri.com/2008/ags"
       xmlns:fx    ="http://ns.adobe.com/mxml/2009"
       xmlns:s    ="library://ns.adobe.com/flex/spark"
       xmlns:mx    ="library://ns.adobe.com/flex/mx"
       xmlns:mxeffects      ="com.adobe.ac.mxeffects.*"
       xmlns:viewer         ="com.esri.viewer.*"
       xmlns:Search        ="widgets.eSearch.*"
       x="600" y="300"
       currentState="textInput"
       widgetConfigLoaded="init()">
 <viewer:states>
  <s:State name="graphicalInput"/>
  <s:State name="textInput"/>
  <s:State name="spatialInput" />
  <s:State name="resultsList"/>
 </viewer:states>

Use one of the other State names instead.

[JimWelsh]

Wow, you are absolutely amazing.  Your dedication is much appreciated and I will look forward to the new version.

[DavidAllen]

Wow, you are absolutely amazing.  Your dedication is much appreciated and I will look forward to the new version.

And I second that! As I learn more about Flex coding, I gain a greater appreciation for your efforts!

David Allen

[RobertScheitlin__GISP]

David,

   Line search tolerance was going to involve a buffer operation which meant a round trip to the server and more time to do the search. So I opted to not do that. 2.2.5 will act much like identify as far as adding a configured amount of screen pixels to the search when using a graphical point search. I think you were the second to ask about this so when more than one person asks for something and it makes sense than I try to add it.

[RobertScheitlin__GISP]

All,

   Version 2.2.5 now available.

Version 2.2.5 - 01/19/2011
  * Added the ability to use coded value domain values in a combobox instead of typing in a text input box.
  * Added configuration option to disable certain titlebar buttons.
  * Added configuration option to set the default search option on widget load i.e. text, graphical, or spatial
  * Added configuration option to add a pixel tolerance to the graphical point search for point on point searches.
  * Documentation pdf for the configuration file is now added.

[JohnGregorovic]

Robert,

Thank you for all of your hard work and also the patience it takes to follow up with everyone's emails

[EricVenden]

Good afternoon Robert,

I tried what you suggested and I still get the same error.  I have updated to your latest version 2.2.5 and still get the same error...any other ideas.

Thanks
Eric

Eric,

   I have been studying your xml and don't see any issue so what I would do is remove all the other fields from the fields list except SUB_NAME and see if that eliminates the error. If it does add the fields back one by one to try and narrow down what the issue is.