New answers tagged tools
I did this on 10. I think the same will work on 10.1 For the properties on my Normal.mxt I made sure that the Read-only attribute was unchecked. I then opened a .mxd and added a custom tool to a custom toolbar and saved the .mxd. I then Verified that Normal.mxt was updated. I then checked the read only attribute on Normal.mxt. For the original .mxd and any ...
The in_memory workspace is usually the way to go for intermediate data and is faster because it doesn't actually write the output to disk. However, you can also define a scratch workspace (arcpy.env.scratchWorkspace) for those tools that don't respect the in_memory workspace or if your result is too big to fit in memory. Esri defines this as a default output ...
One way to handle intermediate data is to use the in_memory workspace. For example: arcpy.Project_management(Footprints, "in_memory", out_coordinate_system) You can specify multiple in_memory objects by adding a name and path separator: "in_memory\temp1" "in_memory\temp2" ... If your datasets are very large and you are worried about cumulative ...
One possibility might be to create a new file geodatabase, set your current workspace environment to it, do your processing, and at the end delete the file geodatabase.
At 10.1 there is a Trim Line and also an Extend Line geoprocessing tool.
It may be that the drawing was in layout view and you're in data view or vice versa. I've done that a few times.
It sounds like you are dealing with a graphic so use the Select tool on the Draw toolbar to select. Then on the same toolbar under the Drawing pulldown you should be able to Convert Graphics To Features so that you can edit it. Alternatively, once you have it selected you can use the Delete key (or Edit | Delete) to delete it. Edit | Select All ...
The tools are in Advanced Editing toolbar. Customize->Toolbars->Advanced Editing Tools.
Top 50 recent answers are included