Sign Up Now
Twitter Facebook Flickr Buzz
PhotoshopSociety.org
 
Search:   
 
Social Networks

LOGIN     

Go
Forgot Password? Go Join Now
Sign Up for Starter's Pack (Free)
Call (800) 223-8720
Email custserv@photoshopsociety.org
 
Need Web Solutions? Get Free Sample Issue

Inside Photoshop: Search Articles

  Search Library:  
 
2018 |  2017 |  2016 |  2015 |  2014 |  2013 |  2012 |  2011 |  2010 |  2009 |  2008 |  2007 |  2006 |  2005 | 
 

Avoid these pitfalls when using Layer Comps

Added on Tuesday 27th of March 2007 01:33 am EST
 

Application:

Adobe Photoshop CS/CS2

Operating Systems:

Macintosh, Microsoft Windows

 

In the article “Presentation is Key! Give your clients what they want with Layer Comps” in this issue of Inside Photoshop, we outlined how to present multiple professional designs to you finicky client by using Layer Comps. But not only are there some things that you can’t record in a Layer Comp, there are some things you can do that will destroy the Layer Comps you’ve already made.

 

Layer Comp limitations


 

As we noted in the aforementioned article, the Layer Comps palette can save layer visibility, position, and the appearance effects applied in the Layer Style dialog box. So where do Layer Comps go wrong? Any of these changes may create a condition that prevents a comp version from displaying the state it recorded:

        If you change the stacking order of your layers, all of your Layer Comps will reflect the new order, possibly creating unwanted changes.

        If you modify size, color, or text, these changes affect the content of the layer. All of your current Layer Comps will reflect these changes. You’ll need to create new layers for these types of adjustments to preserve the existing Layer Comps.

        Smart Objects (in CS2) aren’t such a smart option for Layer Comps. If you create a Layer Comp with a Smart Object, you can’t scale the Smart Object for a new Layer Comp and still preserve its original size in a previously recorded Layer Comp. The original Layer Comp will require the Smart Object in its previous state.

        If you merge layers, delete layers, convert color...