What I mean by locking a layout is making changes to a map and layout combination for a specific task without needing to created both a new map AND Layout when in ArcMap an .mxd drove both.
For example, I’ve got a map template built for a Size A Power point map (which is really common around here). I’ve also got a Size A Layout Template that goes along with the Size A Map Template. I use the Map Template as sort of a “starting Point” where I tailor the map how management wants and then marry it to the Layout Template. (This way all font and symbology sizing works for the size requested). After making the requested changes I export a .pdf or a .emf or a .jpg depending on the requirements of the end product. This work flow requires that each time I received a new request that I make a copy of the map template AND a copy to the layout Template. I must rename both to the name I want for the new map that is required, and thus my project grows by a new map and a new layout for every request I get. (Often I’ll need to revisit old maps to make revision up to years later).
In ArcMap, I also had a Template – an .mxd. I’d take that template and make one copy, adjust the Map view and layout to specs, export to .pdf, .emf, .jpg and All I’d have is another .mxd. Basically it’s one half the “bloat”.
Both workflows accomplish the task – but ArcMap felt more streamlined since it generated ½ the files.
Regarding Legends: I like the functionality that you describe (re-ordering and whatnot) but that’s where it ends for me.
In ArcMap because I just changed elements I needed in the maps and the Layout was locked to that map, I’d never have to re-create a Legend but in Pro because I want to maintain my map template, I need to copy the map, and I want to maintain my Layout template so I have to copy that.
This requires I build a new Legend each time versus having my Legend dynamically update.
When building a new Legend there are no options for a “legend template” so I have to change all legend settings every time I make a new Legend.
In ArcMap since all of my Legend settings were tied to the .mxd, I set the legend settings once and that was it.
Building a new legend in Pro without any template means that every time I do this I need to dig into the settings, set my border properties, background properties, border and background offsets, All Fonts, My Legend title, font-settings, and alignment. Further there is no way (that I’ve discovered) to universally set the font. I have to go into Legend>Title>Font Settings, Legend>Headings>Font Settings, Legend>Labels>Font Settings etc – for every legend setting. Most of the time the font is ALL Tahoma in the legend, but other times it’s all in another font and I can’t figure out why. I don’t necessary mind the UI for the Legends settings if I could set all of them once – for all further layouts, but there is no way to do this (that I have found).
Sorry for the long reply – hopefully that makes sense. So much of what people do in Arc products relies on the industry and the organization itself within an industry. I make all paper maps, but many industries are all digital. In some ways Arc is the Swiss-army of data/maps-representation-of-data. Its understandable that a new flagship programmed from the ground up may not accomplish the same task more efficiently in every possibly way. That said, it feels like ESRI didn’t research real-life work-flows as thoroughly as I’d have liked and threads like this one seem to be proof of that especially as more and more people work on switching over to PRO.
I do appreciate Kory Kramer and other folks efforts sorting through all of these complaints. I just wish PRO felt like the big step forward from ArcMap that we were led to believe. There are certain UI improvements that feel like they are really heading in the right direction (especially if the program was as snappy and quick as we all hoped). Unfortunately, as this thread points out, improvements to speed are lacking. Not just in the specifics mentioned here, but in a LOT of places.
I’ve noticed PRO acting slow when I copy elements in Catalog and Paste them like in my example above, When I change Labeling settings, even when I close a project (like why don’t we have an option for Close and Save the project – one button and done). I can open multiple layouts at the same time but each needs to open – which takes time – and then when I click on the tab – it has to draw which takes more time. I can’t export multiple layouts at the same time so when I make a series of maps that all need to be /pdf’s – I have to run through that export procedure for each map, wait for it to generate the .pdf, and then do the next one. I should be able to export X-number of layouts at the same time to the same format, and close my project while those are exporting. The project may run in the background till those exports are complete – but It should “release me back to Windows” without a wait.
This has turned into a rant but I know others in this thread will empathize.
That said – I reached out to you about specific work-flows because SOME headaches might be alleviated by sharing with one another how we accomplish even basic requests/Tasks using PRO – and anything we do for each other is something ESRI is at least partly off the hook for.
Thanks for sharing your workflow!
Sean
