Default snapping layers not recognized
Hello everyone,
I've noticed that although all of my layers have snapping enabled by default, I have to toggle the snappable layers off then on again for snapping to work.
For example if I open a viewer and select the Draw tool and click Enable Snapping, the circle around my cursor appears but it doesn't snap to anything. I have to then click on Select Snapping Layers and click Clear All (all layers are checked initially) then Select All to toggle the snapping layers off then on again. After doing so, I can snap to features.
Has anyone else encountered this? We're using Geocortex 4.4.3 and HTML5 Viewer 2.5.2
Thanks
0
-
We have also encountered this issue with 4.4.3 and 2.5.2. Has a fix been identified? 0 -
I think the first release of snapping is just going to be clunky to be honest. I ended up having to create a custom JavaScript module because the "EnableSnapping" command was not in the JavaScript libraries. Someone must have forgotten to add the implementation to the code base XD Next release they should do better although maybe I should raise the problem with Latitude about the code base so someone fixes it.... 0 -
@Harold & Claudia, The issue was identified (GVH-8130) and fixed as part of GVH 2.6.
@Matthew, Can you elaborate on the 'EnableSnapping' command not being in the code base? Was this a tablet/handheld issue or something that was encountered in the desktop shell?0 -
This is a desktop issue.
Actually it's "ActivateSnapping". Calling that command from a workflow or JavaScript code results in none of the tools snappnig to layers with snapping enabled.
Additionally when I'm adding a button using the Essentials Manager there is an option for it to run a command. Most commands such as "ActivateBuffering" are available there but not "ActivateSnapping".
To me this indicates there is no implementation or something is not right.0 -
ActivateSnapping can only be executed when a tool is active with a snappable drawmode. A hotkey is configurable and can be used at any to activate and deactivate snapping on the fly ("F" by default). As I mentioned in a previous post, there is an known issue which has been fixed in 2.6 (beta) which may be affecting the functionaility that you see.
There are preconfigured toggle buttons for snapping in the markup, measurement and find data regions. These regions are only visible when a tool is active and display complimentary functionality. These regions are great for indicating when snapping can be used.
Admins are free to modify these regions through the viewer JSON as required. Standalone buttons outside of the regions can be added, but is not recommended in the case of ActivateSnapping as it relies on certain application state to work. If the state is not available, nothing will happen when the user clicks the button.
That being said, there is an inconsistency in how the commands are in the suggestions list in manager. I'll make sure that we get the ActivateSnapping command into the list. Sorry for any inconvenience this has caused you.
Cheers,
Kevin0 -
No problems Kevin and thanks for the reply, we managed fine :) I will leave you with a use case though.
We were trying to allow the user to create a geometry for a feature service _without_ the ability to edit any attributes. Because there are currently no stand alone "edit geometry" tools in GE HTML5 we had to make our own. That worked well except we wanted to snap the drawing of the geometry to a roads layer since the road is what we're concerned about in transport.
So, after activating an edit toolbar I tried calling "ActivateSnapping" expecting Geocortex to handle the interaction between my edit toolbar instance and the enabled snapping layers. This does not work as you've pointed out snapping is _only_ scoped to work with certain GE tools under strict conditions.
In the end it wasn't hard to get it working ourselves but thought I'd give you an idea of how we're using GE. Also a heads up that we are looking for the ability to separate the geometry editing tool from the attribute one. This is because 95% of the time users want a lot of customization to the editing process so attributes are done through a workflow and ediiting geometry is best as it's own button.
Cheers0 -
Hi Matthew,
You guys sounds like you are doing some pretty advanced customizations. Take a look at geocortex.essentialsHtmlViewer.mapping.infrastructure.accessibility.Edit. This is our extended Edit toolbar and snapping should be tied in if you use that.
Cheers,
Kevin0 -
@Mathew
Couldn't agree more with the editing tools as they stand at present. We are simply asking for the Add, Edit features, and Edit Geometry tools to be their own 'buttons' in the UI. The idea that the user needs to hit identify, then guess to hit the options list, and scroll to the bottom to hit the Edit Geometry button just does not make any sense. As for Cut, Union, reshape etc.. I'm only hoping these come along also, and soon, as it's holding us back from migrating to the GVH
@Kevin
Do you have any details/info/demos on the 'extended Edit toolbar' you make mention of, due to said restraints by Matthew and myself....??
Any ideas would be appreciated. We too are looking at having to create our own toolbar to best replicate the UX from the GVS, and even then it falls short of user expectations at this stage.
thanks0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
8 kommentarer