Copy, Clone and Save As
Posted: January 6th, 2020, 8:24 pm
I do a lot of Cloning through the various processes of building an image.
One of the things I have run into is cloning forwards down the branch as opposed to backwards up the branch (as an example, saturating an image, then cloning only a small part of that saturated image back into the previous image). And I certainly understand why that is so.
My workaround for this example is to copy the image, saturate that copy, then clone from the saturated copy into the initial image. And this operation may be a ways down the process branch, after many other transforms.
The issue with this method is, I can't then close/delete the copy and saturated version of that copy, without receiving the warning that everything downstream will also be closed/deleted. Even if I save the other image that I just cloned into, that image will be closed (not deleted if saved of course) as well. This then forces me to find that image and re-open it to continue working on it.
During other image processing routines, I regularly save an image and wish to close everything upstream, but leave the last (saved) image open on screen, as I often find the branch getting way too long and unnecessary.
My question is: Is there a way, and if not, could it be done, so any saved image farther downstream of an about-to-be-closed image, be left open, or at least an option be presented that allows one to choose to keep that image open. Or is this too onerous??
Marv
One of the things I have run into is cloning forwards down the branch as opposed to backwards up the branch (as an example, saturating an image, then cloning only a small part of that saturated image back into the previous image). And I certainly understand why that is so.
My workaround for this example is to copy the image, saturate that copy, then clone from the saturated copy into the initial image. And this operation may be a ways down the process branch, after many other transforms.
The issue with this method is, I can't then close/delete the copy and saturated version of that copy, without receiving the warning that everything downstream will also be closed/deleted. Even if I save the other image that I just cloned into, that image will be closed (not deleted if saved of course) as well. This then forces me to find that image and re-open it to continue working on it.
During other image processing routines, I regularly save an image and wish to close everything upstream, but leave the last (saved) image open on screen, as I often find the branch getting way too long and unnecessary.
My question is: Is there a way, and if not, could it be done, so any saved image farther downstream of an about-to-be-closed image, be left open, or at least an option be presented that allows one to choose to keep that image open. Or is this too onerous??
Marv