This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(150.4, 28.000000000000004%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMP%3C/text%3E%3C/svg%3E)
There was a question 2 years ago in relation to attaching a handler to a DragHandle's click event. Is it not possible still to attach an event handler to DragHandle's events, specifically when dragend is triggered?
For further clarification, I have 2 capabilities I'd like to implement whilst editing a polygon:
Both capabilities require me to know the final position a user has dragged the handle to, such that I can determine a course of action and modify the target position (for option 1) or modify the shape entirely (for option 2).
An Azure service that provides geospatial APIs to add maps, spatial analytics, and mobility solutions to apps.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 74%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EAM%3C/text%3E%3C/svg%3E)
@Mark Phillips Thanks for your query. Community SME's on this topic or our team will review your scenario and circle back at the possible earliest time.
There is no events for the drag handles. You can monitor the drawing start/end/change events and monitor the coordinate arrays to determine which vertex changed. That said, it sounds like you want to snap the coordinate, in which case, it is best to use the built-in snapping capability that does this already and is highly optimized for performance.
That might work for snapping to another polygon's position however I really want the snap to occur whilst in edit mode, and I'm assuming here those events fire after edit is done? For use case 2, which is effectively a delete vertex function, this must occur whilst in edit shape mode.
I've written some code that achieves a delete vertex behaviour by modification of the existing EditHelper to achieve a "demote" capability, triggered by dragging a vertex handle within a pixel threshold of an adjacent vertex handle. Not sure if the code mods break any licensing though as it requires me to download and modify the existing non-minified js. Are you a member of the dev team and interested in the code to perhaps use in the SDK? Not sure where to offer it up is all.
I'm the original program manager for this feature and had this as a feature on the roadmap but I changed teams a few years ago and this feature hasn't been advanced beyond its original set of features. Talking with the new program managers, advancing the drawing tools capabilities is lower priority to many other features they have on their list unfortunately.
I appreciate your efforts to find out the progress, or lack there of. With the knowledge that the team are not going to add this functionality, am I precluded from doing the following explicitly. I ask as the license header in the js file is long and I'm no expert, however section 4a-e makes me think that I would not be able to provide this change.
I realise, from your stackoverflow response, that this may break functionality in the future by using undocumented functions and behaviours. This is something that I'd have to manage in time. I can only deal with requirements I have today.
I appreciate your input on this I have no intention of breaking any agreements, implied or otherwise.
You can go down that path, but as noted, there will be the potential for something breaking in the future if you use any undocumented API's in your modifications. If you use the documented API and modify/host the changed code (and CSS file) there should be low risk (can't say for 100%).