How hard would it be to include the locator widget into this as a tab?:confused:If you are talking about adding geocode service capability (i.e. locator widget type functionality) into this widget then I would have to say probably not going to happen. I am attempting to maintain the true intent of this widget (a search widget). The code base for this widget is already larger than any publicly available widget out there and is getting hard to test all of the different configuration possibilities that currently exist. I am in the process of developing an Enhanced Locator widget that I could make to have a tie in with the eSearch, like I do with the eDraw and Point Buffer Widget. If you are looking for the ability to locate and address and then use the eSearch to search based on that location point, then that is a possibility.
<multipartgraphicsearch>false</multipartgraphicsearch>
Michelle,
Are you saying you actually made code changes or you just used the configuration tag for this?<multipartgraphicsearch>false</multipartgraphicsearch>
I tested by setting the configuration as above, disabled text,spatial and allowed the URL search to select some layer, changed the search layer, choose a graphical selection tool and selected some features and it all worked fine.
Is there some step that I am missing from what you are doing?
Michelle,
OK, Can you send me your URL parameters (i.e. &esearch=COMMERCIAL&slayer=0&exprnum=3)?
Here is my test steps:
- disabled text,spatial buttons (I don't think the visible="false" setting on the spark checkbox is significant for this test).
- set multipartgraphicsearch = false
- set the URL search to search some feature in the first layer using the 4th expression
- Using the same layer that was used by the URL search I choose a graphical selection tool and selected some features.
and it all worked fine.
esearch=ANTI_MD-02140501_POTOMAC RIVER_NON-TIDAL 8-DIGIT WATERSHED&slayer=0&exprnum=0
Michelle,
Just so that you know if you do not specify a slayer and/or a exprnum then my code just default to searching the first layer in the eSearchWidget.xml and using the first expression setup for that layer. So what you are doing is shorthand for thisesearch=ANTI_MD-02140501_POTOMAC RIVER_NON-TIDAL 8-DIGIT WATERSHED&slayer=0&exprnum=0