Latest Contributions by AdamForknall

Currently, the New Table dialogue allows entering only the Field Name and Data Type in a tabular format. Once that is done, the user must click an option in the Field Properties pane to make changes to those properties. This results in unnecessary movement from keyboard to mouse to keyboard. The Field Properties should be move to be columns next to Field Name and Data Type, so that all data entry can be done intuitively and without needing to move from one table to the other. ... View more

Currently, the New Table dialogue allows entering only the Field Name and Data Type in a tabular format. Once that is done, the user must click an option in the Field Properties pane to make changes to those properties. This results in unnecessary movement from keyboard to mouse to keyboard.   The Field Properties should be move to be columns next to Field Name and Data Type, so that all data entry can be done intuitively and without needing to move from one table to the other. ... View more

Adding a layer to the legend requires more effort than it should, if the legend is set to not automatically add new layers. Instead of having to click through 3 or 4 menus/dialogs, it would be ideal if a layer could be right-clicked in the Table of Contents, and the option "Add to Legend" be presented if a legend is existing in the layout. ... View more

The ability to export and import labels would be very handy. It's not always appropriate to copy a layer to another map document, so the ability to import/export labels would be great. Options to export either all labels for an MXD, labels for a layer, or certain layer classes to something like a text document for import into another mxd would be very useful. ... View more

It would be nice to be able to set certain feature datasets, feature classes, tables or rasters inse a Geodatabase as Read Only to prevent modification, without the need for using an enterprise GDB/arcSDE with user permissions etc. Just a local implementation, similar to the Read Only and Hidden attributes which can be set on a file within Windows. ... View more

It would be nice to be able to set certain feature datasets, feature classes, tables or rasters inse a Geodatabase as Read Only to prevent modification, without the need for using an enterprise GDB/arcSDE with user permissions etc. Just a local implementation, similar to the Read Only and Hidden attributes which can be set on a file within Windows. ... View more