SHARED LAYERS ACROSS PAGES

[yomilky]

Badass Designer roadmap. Please at least review how Fireworks implements shared layers across states (which I have been misusing as pages for years). It's the most powerful implementation of a layer - sublayer - "page/mock" relationship I've seen; suppose you need a main menu across 10 pages/mocks, but you have a 20-page doc. You simply “share layer to states”, then hide it from those pages you don't want it on. All updates to that layer appear on all states (again, as pages) without absurd asset duplication cause by art boards. If you need unique menus, you can simply hide that layer and make another, or unshare the layer and decide which pages get that content. It works like a symbol but with the advantage of edit in place and locking certain sublayers if needed.

[fwallenberg]

I have a similar need but a different use case. I'm using AffDes for wine labels. There are some objects that are shared by all labels ... easy. However, there are other objects that are shared by some, but not all (or rather, there are a few different versions, one of which is present on each label). Currently I have a common layer, a couple lf "alternatives" layers and then one layer per specific label. This allows me to not have to duplicate the alternatives content in each label (and therefore allow me to ensure that any change is carried over to all of them). What it does force me to do is to go through and check multiple layers and objects when I want to display a specific layer. 

 

What I'd like to see is a separate list of "pages" that each is predefines to turn on/off certain layers and objects. That way I can quickly and easily switch between the labels (pages).