2005-06-10 15:23:00
a long shot I know...
thanks :
Jon
thanks :
Jon
#1
a long shot I know...Nope.
thanks :
Jon
a long shot I know...
a long shot I know...
thanks :
Jon
a long shot I know...
thanks :
Jon
a long shot I know...
thanks :
Jon
A screen shot with the whole history palette placed as a new layer on the bottom of your layer stack make an easy replacement if named "history palette" and if you have a big disk.
"KoperniK" wrote in message
a long shot I know...
thanks :
Jon
I notice there is an option in General Preferences for a 'History Log'. I presume this saves the history as a text file - I haven't tried it though. Could be useful?
In article
<42aa1a21$0$27632$
com.au>, says...
"KoperniK" wrote in message
a long shot I know...
thanks :
Jon
I notice there is an option in General Preferences for a 'History Log'. I presume this saves the history as a text file - I haven't tried it though. Could be useful?
Yes it does, and is useful - to a point. You can see exactly what was done,
and possibly re-do it, if need be. Unfortunately, there is not a function to
save a "usable" History Palette, so you could just choose a point to go back
to. Saving different iterations of a file is about as close as you can come,
as has already been outline in this thread.
Hunt
A screen shot with the whole history palette placed as a new layer on the bottom of your layer stack make an easy replacement if named "history palette" and if you have a big disk.
But this won't allow you to go back in history. This is why people often save things to a new file after every few iterations. And the use of layers
can really help here too. If something can't be "undone" after the image has been saved, just duplicate the layer (or image) before you apply whatever you want to do.
--
Martijn
http://www.sereneconcepts.nl
"Martijn" wrote in messageSnapshot goes away after the file is closed.
A screen shot with the whole history palette placed as a new layer on the bottom of your layer stack make an easy replacement if named "history palette" and if you have a big disk.
But this won't allow you to go back in history. This is why people often save things to a new file after every few iterations. And the use of layers
can really help here too. If something can't be "undone" after the image has been saved, just duplicate the layer (or image) before you apply whatever you want to do.
--
Martijn
http://www.sereneconcepts.nl
Shouldn't the snapshot feature fulfil this requirement?
Caitlin wrote:
"Martijn" wrote in messageSnapshot goes away after the file is closed.
A screen shot with the whole history palette placed as a new layer on the bottom of your layer stack make an easy replacement if named "history palette" and if you have a big disk.
But this won't allow you to go back in history. This is why people often save things to a new file after every few iterations. And the use of layers
can really help here too. If something can't be "undone" after the image has been saved, just duplicate the layer (or image) before you apply whatever you want to do.
--
Martijn
http://www.sereneconcepts.nl
Shouldn't the snapshot feature fulfil this requirement?
--
"Hunt" wrote in message
In article
<42aa1a21$0$27632$
com.au>, says...
"KoperniK" wrote in message
a long shot I know...
thanks :
Jon
I notice there is an option in General Preferences for a 'History Log'. I presume this saves the history as a text file - I haven't tried it though.
Could be useful?
Yes it does, and is useful - to a point. You can see exactly what was done,
and possibly re-do it, if need be. Unfortunately, there is not a function to
save a "usable" History Palette, so you could just choose a point to go back
to. Saving different iterations of a file is about as close as you can come,
as has already been outline in this thread.
Hunt
Or alternately you can save snapshots at key points in your file - rather than save multiple files.
Or alternately you can save snapshots at key points in your file - rather than save multiple files.
Scratch that - I'm wrong!
Why doesn't Adobe add a 'Save History' option to PS?
I assume that adding the history states creates huge files. Is this the only reason or are there other difficulties?
On Sat, 11 Jun 2005 13:01:42 +1000, "Caitlin"
wrote:Or alternately you can save snapshots at key points in your file - rather than save multiple files.
Scratch that - I'm wrong!
Sort of. If I get to a point which is worth saving as a snapshot I also save the image there. Before I've finished working on an image I may have 20+ saves in the image folder. Disk space is cheap - my time isn't ;-)
--
Hecate - The Real One
Sort of. If I get to a point which is worth saving as a snapshot I also save the image there. Before I've finished working on an image I may have 20+ saves in the image folder. Disk space is cheap - my time isn't ;-)
That IS the best way to get around the History problem. Fortunately, NOW, HDD real estate is cheap, AND available. There was a time, that I had to do a tape bu of each version (even before DAT), because my disks were full, just from the image, and the Scratch Disk. Talk about slowing down the creative process !!! But, those days are now long gone, thankfully.Yeah, I remember tape. It was that stuff you backed up to that wouldn't play back in other device but the one you recorded on (not even another exact same device from the same maker); would mean that all your backups were dead as soon as the tape device died; and would actually occasionally allow you to recover an uncorrupted file if you were lucky ;-))
On 13 Jun 2005 16:55:09 GMT, (Hunt) wrote:[SNIP]
Yeah, I remember tape. It was that stuff you backed up to that wouldn't play back in other device but the one you recorded on (not even another exact same device from the same maker); would mean that all your backups were dead as soon as the tape device died; and would actually occasionally allow you to recover an uncorrupted file if you were lucky ;-))
--
Hecate - The Real One
Yeah, I remember tape. It was that stuff you backed up to that wouldn't play back in other device but the one you recorded on (not even another exact same device from the same maker); would mean that all your backups were dead as soon as the tape device died; and would actually occasionally allow you to recover an uncorrupted file if you were lucky ;-))
Yes, that's the stuff! You DO remember tape - and I thought you much too young. Surely, your mum told you about that stuff? <G>
I'll be heading off to Mayfair soon, and if I see a young lady, wise beyond her years, doing stock shots (another thread) in Green Park, I'll introduce myself and say Hi.<g> It'd be a pleasure, I'm sure.