topic Re: Subtle problem with IEditSketch in ArcObjects SDK Questions

Subtle problem with IEditSketch

StevenHill1 — Wed, 10 Apr 2013 00:51:05 GMT

I have a set of tools (inherited from BaseTool) developed in VS2008 C# for ArcMap 9.3. One of the tools (call it Tool A) uses the editsketch to create a polygon which is then added as a new feature to a feature class (call it feature class A). The edit operation is stopped at that point. Then in another tool (call it Tool B) I again use the edit sketch to draw a polygon which is used to select point features and perform some operations on them (I do this because it is easy to set up the edit sketch geometry and capture the FinishSketch event to get the edit sketch geometry). However, the first time I use the edit sketch in Tool B after creating a feature with Tool A, the polygon that I create to use as a selector is added as a new feature to Feature Class A. It's as if the double click event that finishes the sketch in Tool A is still hooked to the event, even though the editor has been stopped and a (supposedly) new edit sketch has been started.

Does anyone have any insight into why this is happening, and maybe a solution?

Re: Subtle problem with IEditSketch

Anonymous User — Wed, 10 Apr 2013 16:27:36 GMT

Steven,

When you activate tool B your edit task may still be set to create feature with the edit target set to layer A.
When you finish the sketch in tool B the editor will do whatever the current task is, using the current sketch geometry.

When you activate tool B you can set the editors current task to null and then do your selection code in the finish sketch event.

_editor.CurrentTask = null;

Back in tool A, if your creating your own feature and storing it in the finish sketch event, you should set the edit task to null when you activate the tool to prevent the editor from creating two features.

Re: Subtle problem with IEditSketch

StevenHill1 — Sat, 11 Dec 2021 17:15:09 GMT

Hello Sean:
Thanks for the suggestion, but unfortunately it did not solve the problem. Here is the code that sets up the edit sketch. It's the same for both Tool A and Tool B.

                    m_editSketch = m_editor as IEditSketch2;
                    m_editSketch.GeometryType = esriGeometryType.esriGeometryPolygon;
                    m_editEvents = (IEditEvents_Event)m_editor;
                    m_editEvents.OnSketchFinished += new IEditEvents_OnSketchFinishedEventHandler(m_editEvents_OnSketchFinished);
                    m_editor.CurrentTask = null;

A little more information that might be helpful: if I put a breakpoint on the OnSketchFinished event for tool B, on entry to the event handler the editor and the edit sketch are null items, so the edit sketch geometry is null as well - as if the editor and edit sketch have been consumed by some event handler left over from Tool A.

Re: Subtle problem with IEditSketch

Anonymous User — Wed, 10 Apr 2013 21:49:04 GMT

ok. Make sure you are also unsubscribing from the finish sketch event in the tool's deactivate method.

public override bool Deactivate()   {     // Unsubscribe events     m_editEvents.OnSketchFinished -= m_editEvents_OnSketchFinished;     return base.Deactivate();   }

Re: Subtle problem with IEditSketch

StevenHill1 — Thu, 11 Apr 2013 04:03:29 GMT

Thanks so much for replying Sean, that fixed the problem.