topic Re: How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc. in ArcGIS Pro SDK Questions

How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

Gurunara — Thu, 11 Jul 2024 20:33:42 GMT

How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

Also how to determine when a new GraphicElement is added or existing ones are deleted?

Re: How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

GKmieliauskas — Fri, 12 Jul 2024 07:37:17 GMT

Hi,

There is ElementEvent. Event argument member Hint has some different states for changes: ElementAdded , ElementRemoved, PlacementChanged.

Re: How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

Gurunara — Sat, 13 Jul 2024 08:51:28 GMT

Some samples...

https://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic76581.htmlhttps://pro.arcgis.com/en/pro-app/latest/sdk/api-reference/topic76581.html

Re: How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

Gurunara — Sun, 14 Jul 2024 17:13:18 GMT

There is some issue with using ElementEvent.Subscribe(args =>

{

if (args.Hint == ElementEventHint.PlacementChanged)

});

This event gets triggered hundreds of times on a single move of a graphic element (not during but at the end of the move).
Is this a bug... and any way to prevent this so only one event is handled at the end of a move..?

Re: How to determine when a GraphicElement in a GraphicLayer gets edited, resized, moved, etc.

Gurunara — Thu, 18 Jul 2024 18:00:06 GMT

Looks like there are properties for various attributes that could change, and have to check to see if any one of them have changed, each of which is generating an ElementEventHint.PlacementChanged event...

but they seem to be private properties, i.e. for each element in ElementEventArgs args.Elements, examine _placement... so may have to do it using reflection...

for now just by placing a delay of 2 sec after handling for the first placment event before allowing next one to be handled... seem a good enough workaround...