How to pass data to an ArcMap extension?

Question

Hello experts,

I try to find a hint, how to pass some data (a session id, user name etc.) to an ArcMap Extension. I could use a file or the registry, but I assume there is a more elegant "in-memory" way?!

Perhaps I am just missing the right term. What I try to achieve is the following:

The data originates from a desktop application which shall start ArcMap and activate the editing via the IAppRot Interface.

I have an editor extension in ArcMap with an event wired to the "OnCreateFeature" editor event. When this event is fired, some of the attributes of the recent feature shall be automatically filled.

Has anybody done sth. comparable or is there any "best practise" to consider?

Any hint is appreciated. Thanks in advance.

Regards
Fossi

FossiG_ · Answer

Ah, okay. So your AddIn creates this dockable window und the COM-Class determines its handle and writes to it. And the onCreate in the AddIn does the same gets the handle of the window and reads the data. I think I've to dig deeper into these window extensions.
 [...]You can expose some public properties of your extension?

Umm, I don't know. Haven't done something like this so far. Public properties of an ArcMap extension? Or are we talking about the other side, the assembly or in your case the COM-Class?

TIA
Fossi

D_Hornby_ddh_uni · Answer

My dockable window has drop downs/buttons to control what the user needs to do.  I can get a handle on it and write the ID infomation to it. The editor event captures the onCreate of feature and then goes searching for the dockable window. You can expose some public properties of your extension?

FossiG_ · Answer

Duncan! Sorry, shame on me. *blush* I'm a bit off today.

Okay, let me try to recap and I beg your indulgence.

1. Access creates instance of COM-Class [lets call it COM]

2. Access calls COM.StartEditing with Argument IApplication -- that is a pointer to the ArcMap.Application also started by access, right?

3. COM.StartEditing gets handle on Editor through the IApplication pointer and starts edit session.

4. An ArcMap AddIn Extension listens for edit sessions.

So far - I am fine. I got an Assembly which implements the IAppRot, thats quite comparable to your COM-Class. And I got an  editor extension with OnCreateFeature-Event, too.

5. Edit event "writes an ID which was written to a dockable window to the feature". Umm, stop! Here comes the concept, that is new to me. You use a dockable window as a temporary storage?

Haven't used them before, just scanned the "Simple logging dockable window with a custom context menu" sample (http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#/Sample_Simple_logging_dockable_window_with_a_custom_context_menu/00010000048s000000/). I assume they they can store structured data, too?! And you hide it, or do you leave your window visible?

Looking forward to here more, thank you in advance!
Fossi