ShowFeatureDetails Command
Hi,
I'm noticing a difference in how the 'ShowFeatureDetials' viewer command behaves between our production server (essentials 3.15\htmlv 1.3) and our test server (essentials 4.2.2\htmlv 2.3.3). I have long description configured with a link to execute this command. Previously, it would simply display the details interface. At the new version it displays the details interface but also zooms and highlights the feature.
Anyone know, is this change by design, or is it unintentional? It is problematic for my app, as I want to provide separate links in the long description for: 'Show Details', 'Zoom to Feature' and 'Highlight Feature' (I also disable the default behaviour of clicking anywhere in the result to see details). The logic here is that a user may want to see the details for a feature without zooming to it on the map.
Thanks
-
I am not sure about past versions for Essentials, but I am using Essential 4.2/HTML 2.3.3
I am doing "almost" the same thing with my results list, in my long description I have 'Show Details' and 'Highlight', however I still want my users to ZoomToFeature when they click on the item. I have modified the Desktop.json and changed the parameter values for ResultsListFeatureClickedEvent... and only have ZoomToFeature listed.
The default had ZoomToFeature, HighlightFeatureDetails, and ShowFeatureDetails.
I would think if you removed ZoomToFeature, you would get the desired action?
0 -
Daniel, thanks for the reply. I had already altered the config for ResultsListFeatureClickedEvent as you described, so that there are no events, not even 'ZoomToFeature' listed. This works as expected. When a user clicks the result nothing happens. The problem is when they click the link for show details, it shows the details but also zooms and highlights.
You have a link for 'Show Details' in your long description. Assuming this executes the viewer command 'showfeaturedetails'? When a user clicks that, does the zoom\highlight behavior happen too?
0 -
Latitude confirms this is a bug at v2.3 of viewer. Upgrading to v2.4 fixes it.
0 -
This bug seems to be back at 2.7 version of viewer. 0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
4 Kommentare