nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Creating toolbar text inputs to auto populate fields on feature creation

StevenHaslemore

Hi,

I want to setup a toolbar that users can input the common details about a particular edit session, such as install date, as built document reference, etc etc

And then have these values auto populate the corresponding fields across the range of features created.

This seems like the place to start http://help.arcgis.com/en/sdk/10.0/arcobjects_net/conceptualhelp/index.html#//000100000391000000 (Building editor extensions using add-ins)

But I get the impression that simple text inputs are difficult to put in the toolbars?

I've not worked with ArcObjects before but if someone could outline if it's A. possible and B. a general approach then it would be a great start.

Or is this something that could potentially be acheived with python add-ins.

Thanks for your time!
Steven

Encuentra más publicaciones etiquetadas con

Accepted answers

All comments

StevenHaslemore

Thanks for your thoughts Leo,
It's a starting spot to investigate.

This posting seems to cover some similar ground too on further poking around
http://forums.arcgis.com/threads/30280-ArcGIS-10-Addins-write-to-a-form

LeoDonahue

I can't find the .NET equivalent of this:

http://help.arcgis.com/en/sdk/10.0/java_ao_adf/conceptualHelp/engine/0001/000100000350000000.htm

StevenHaslemore

that sounds like it could fit the bill.

I'm still not sure where I would start with this approach.

LeoDonahue

Then maybe you could do a small dockable form with a text inputs for those values?

StevenHaslemore

I suppose you could simplify it down to that.

A key part is not wanting to put a dialog box box between the button press and the action on the features, and that the values could persist across multiple runs of the process.

It will also be required to fetch an id value for each feature from a webservice.

Thanks

LeoDonahue

so then it becomes more of a mass field calculate tool?

StevenHaslemore

The linked walkthrough talks of the OnCreateFeature edit events during an edit session which was one option, or if the overall approach was simplified to a python add-in then a workflow of selecting the required features and clicking a button would also be considered.

LeoDonahue

And then have these values auto populate the corresponding fields across the range of features created.

What event would trigger this? A button? A stop editing event? You could read in a properties file instead of using a text field in a toolbar - maybe?

Únete a la Conversación

Los miembros registrados pueden publicar, seguir actualizaciones y más. ¿Nuevo aquí? Regístrate gratis.

Enlaces Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.