Cloned variants
I often create a cloned variant of an image. COPro allows me to edit that clone as a totally independent image. I can assign it different keywords. I can select the original or the clone image independently in a smart album by use of keywords for example. However if a smart album ends up with both images I am not able to position the clone image without it "dragging" the original one with it.
In effect I'd like to create a totally independent image as far as COPro is concerned. Is there such a thing without duplicating the image outside of COPro and importing both?
I see another poster has asked the same question- almost - I'm interested only in allowing a different position within a smart album not that they select both.
In effect I'd like to create a totally independent image as far as COPro is concerned. Is there such a thing without duplicating the image outside of COPro and importing both?
I see another poster has asked the same question- almost - I'm interested only in allowing a different position within a smart album not that they select both.
0
-
You probably should create a Support Case entitled "Enhancement Request: .... summary of request ...."
This way Phase will be able to assess the level of genuine interest in such a development.
My guess is that to do what you would like would require some considerable re-design of the application and add some complexity if both (or indeed all because many would be presumably be possible) variants needed to be managed as one by some people in some situations and yet separately in others.
The simpler solution, available today, is to duplicate the original, perhaps with a revised name, and have a clearly identifiable uncomplicated way to manage administer the images when separate administration is required.
However I do appreciate that if one almost always creates variants that one needs to manage separately the storage overhead could be unacceptable.
Grant0 -
Thanks Grant, I suspected as much. I will create an enhancement request as you suggest.
Robin0
Post is closed for comments.
Comments
2 comments