Slice layers? (not slicing them)

np - works well if you combine that feature with with Layer Comps also..
Multiple Designs in a single file accessible to a single click.

cheers
heathrowe

i still think its useless

chris

perhaps you don't design for clients on a regular basis!
perhaps you've never been asked to have something modified on the fly!
perhaps you never used it, thats why its useless to you.

this is godsend, fig
heathrowe

I back you up on that heathrowe

luckily i'm not the easily offended type...

a) i wasn't making an extremely serious comment, hence the smiley

b) i'm probably one of the most experienced folks on the board, have been designing professionally for 8 or so years now and do pretty much straight client work (to the point where i wish i had time to do my own stuff)

c) i still don't see any good use for it. i can't come up with an instance to where i'd have a layout that would have to be resliced so dramatically that having an alternate saved layer set would be useful. i also always save in iterations so that i have an older, unchanged copy of the work at a certain point and that if a newer version of the file i do have gets corrupted (which absolutely can and does happen) i still have an intact version.

chris

hey - it wasn't my intent to offend -

and on the same topic " I also always save in iterations so that i have an older, unchanged copy of the work at a certain point" >> thats the whole point.
Using combinations of Slice Sets, Layer Comps, and in particular with Version Cue, theres no need to save iterations (Version Cue does that for you and without the risk of overwrite). Basically, what it boils down to is economic workflow and accessibility without having to juggle your hard drive for previous or various versions of a design.

cheers
heathrowe

no prob, didn't figure you did, just came off as a bit condescending

and i understand what you're saying, but my point is that saving in iterations allows me to have a back-up copy of the files i'm working on. sure, it may take up a bit more hd space and make me look for a file occasionally (tho if i've got a naming convention, which i do, it shouldn't take that long), but the real key is that i've got a back-up in case i lose a file, a file is corrupted, etc., knowing that we don't all quite back-up our work regularly like we should. at least i don't

chris

Hi, I'm sure none of you care but...

I have to agree with fig on saving multiple iterations of files, I do it all the time and in that I just had a hard drive crash it saved my @$$. Well most of the time, The files I hadn't begun working on had no backups at the time.

Sucks.

Sorry for my 2 cents, just want to feel useful.

I'll just go off now on my own...