Latest Contributions by RhettZufelt

I am using the FV3.6 with the EditWidget and AttributeWidget.  I have the edit widget to only allow attribute updates, no add or delete features, no merge, update, geometry, nothing but <updateattributes>true</updateattributes>. In the edit widget it appears to honor it.  If I have the edit widget open and click on a feature, the popup allows me to modify the attributes that I have configured, and nothing else.  If the edit widget is open, and I expand the table from the attribute table widget, I can also modify the attributes directly, but only if the edit widget is open (on editable feature layers).  Fine, this is what I was expecting to see.  However, if I have a feature selected in the edit widget, the attribute table widget gives me the option to "Delete Selected features", and if selected WILL delete the feature, even though the edit widget is set to not allow that. So, where does the attribute table widget get it's options of what it is allowed to do?  Is there a way to make it honor the layer settings so that it is not possible to delete a feature from the attribute table widget? Also, when I select a feature with the edit widget, it will also select that feature in the attribute table, which is nice.  However, now and then, it doesn't work, and I need to close/re-open the edit widget one to many times (sometimes a refresh of viewer) before it works like that again, and will just select in the edit widget, and not pass the selection on to the attribute table widget.  Any ideas as why this is happening and/or how to fix? Thanks for any help, R_ ... View more

Again, from the documentation: <result>The container used to configure the search result's pop-up, [added at 3.5.] It has the following child tags: <title> Text title displayed in the resulting pop-up. <description> Text description displayed in the resulting popup. You can configure the <title> and <description> using custom description functionality that allows you to display pop-up content using a custom sentence or paragrah structure and supports field substitution using a {FIELD} style syntax. This seems like a nice option, however, it appears as if it is a child of the <geocoder> tag.  Seems like it should be a child of the <mapservice> tag, especially since it allows the description type custom popup info. Doesn't make sense to me to have this under the <geocoder> tag unless ALL your locator/mapservices have the same attributes, etc. The example in the documentation ArcGIS Viewer for Flex‌ is for a live traffic feed.  However, if I try to use something similar, but also want to use mapservices, OR, just mapservices but more than one, it will show a popup "template" but will not populate it unless they all have the same attribute names. So, if I search my sewer manholes and have it set as such:    <result>       <title>Search result for {FacilityID}:</title>       <description>          <![CDATA[Popup for {FacilityID}            <img src="{URL}" width="130" height="100"             hspace="0" vspace="0"/>]]>       </description>    </result> Then search for a sewer manhole, I get: If I then enter a street name in the same search box, I get: Since there is not a FacilityID field in the streets layer the variables aren't substituted. Am I just using this wrong, or is it pretty much only useable with only one geocoder and/or all searched services have the same schema (or at least fields)? Thanks, R_ ... View more

From the headercontroller documentation: <name>Name given to the layer when displaying the search results, default behavior is to display the layername. [Added at 3.2] Seems that when I put the <name> tag in my headercontrollerwidget.xml it appends the name value after the layername, not instead.          <mapservice>             <url>http://arcgisprod01.ci.richland.wa.us/ArcGIS/rest/services/PublicWorks/SDmanholes2Bnumbered/MapServer</url>             <layerids>2,3</layerids>             <searchfields>FacilityID</searchfields>             <name>Storm Feature</name>          </mapservice> Am I missing something here, or is it going to still add the layername as well as any name tag values? R_ Using OTB compiled FV3.6 ... View more