Layer Comps - why not include the canvas size as well? It's all that's missing. Also, if you do include it, please don't forget us CS5 peeps (maybe through an update).
- 2 Posts
- 0 Reply Likes
Posted 8 years ago
Jeffrey Tranberry, Sr. Product Manager, Digital Imaging
- 15079 Posts
- 2148 Reply Likes
Canvas size is a destructive change for documents with Background layers.
- 2 Posts
- 0 Reply Likes
Right. But wouldn't something like:
"Note: Activating this feature will cause destructive changes to background layers. Do you wish to continue?"
be a possible option?
Not trying to be funny though. When we do designs for the web, we've basically fully embraced layer comps, and I know a number of other web designers who have as well, and it goes without saying that canvas sizes tend to vary a great deal from page to page (i.e. blog roll vs about).
"Note: Activating this feature will cause destructive changes to background layers. Do you wish to continue?"
be a possible option?
Not trying to be funny though. When we do designs for the web, we've basically fully embraced layer comps, and I know a number of other web designers who have as well, and it goes without saying that canvas sizes tend to vary a great deal from page to page (i.e. blog roll vs about).
Jeffrey Tranberry, Sr. Product Manager, Digital Imaging
- 14841 Posts
- 2022 Reply Likes
Yup. We could probably do some error handling like that - and suggest the user to promote their background layer to a floating layer, or auto-magically do it. I'm just thinking through to problems that would be 'gotchas.' There was another request to save multiple crop selections in a document. We'd have to store meta-information like that to make this work. It's not currently part of the state model.