Yesterday on a map I had to make the patches are larger than normal, because that was the only way for them to show the hatching which is quite widely spaced. If there was a way for the patches to always show the hatching, regardless of the spacing, then I wouldn’t have to bother with increasing the patch sizes. This was a problem in ArcMap also and you need to improve your product with an option to scale the symbology in the patch, in a manner decoupled from the hatch spacing in the layer symbology settings, so that the legend is always clear. It is usually not the case that different hatch spacings are used between layers and, for example, the colour is kept the same, so it is not necessary to replicate the hatch spacing in the legend. What is more important is to show the hatch colour and because the legend mindlessly replicates the hatch spacing in its tiny patches, usually they don’t show. I would prefer the standard hatch spacing in the tiny legend patches to be 3-5 points. Then the reader will see plenty of hatches and get a confident read on what to look for on the map. I have been doing GIS for about 10 years and I’m speaking from long experience here of this problem. The work around is to create another layer specifically for the legend with smaller hatch spacing, but do you really want to make you users do this?
... View more
ArcCatalog should be able to access all of the elements used in any given mxd. For example ArcCatalog should have access to a legend saved in a mxd for drag-and-drop into a newly composed mxd (perhaps though a Style Manager type interface). Any all objects, whether graphic elements, or feature classes, etc. should be exposed to ArcCatalog for utilization in newly composed mxd's.
... View more