Is there a way to turn off the simulated symbol transparency in the legend? In ArcMap it is done simply via the dataframe properties via the 'Simulate layer transparency in legend' checkbox, but I've looked everywhere and I cannot locate it in ArcPro.
Thanks,
Nigel
Nigel,
I'm not sure if this is the same thing as what you are looking for but, go into the Color Properties of the symbol and you can adjust the transparency in there:
Hi Adrian
Thanks for your response. No, I can style each symbol by its transparency and the layers, but in the legend the symbols for the layers are also transparented based upon the layer. I want to keep the transparency on the map but not have it transparent in the legend. Does that help to clarify things?
Thanks,
Nigel
That does make more sense. Take a look at this thread that mentions this topic. I think it can help:
oh, whoops, or just read what Dan wrote, haha! (I didn't hit refresh)
a link, other than transparency links to specif objects
http://pro.arcgis.com/en/pro-app/help/mapping/layer-properties/vary-symbology-by-transparency.htm
Hi Dan and Adrian
Thanks. It then appears this is a 'glitch' to workaround the legend transparency issue. Good to know and hopefully someone else will find it useful as well.
Cheers,
Nigel
Using or not using layer transparency in the legend was a simple toggle in ArcGIS. Is there any new info on this topic? I generally never simulate layer transparency in my legends (in Desktop), so not having an option in Pro seems like, yet again, a major oversight (there are so many of these!). I'm really forcing myself to use Pro for exhibit production lately but the UX is pretty lacking. I'm constantly having to toggle things on and off to get to the desired options, you have to find complicated work-arounds for things that used to be built in. . . it still seems like a there are major steps backward with Pro. Increased familiarity with the program isn't necessarily helping either- it's just kinda reinforcing this for me. Most of my internet searches just turn up results from other long-time users complaining about the same things.
Do we have any update on this request from ESRI as yet, as to when it may be employed or a workaround?