> What the patch does is to force the writing and reading of an ID-type file > whose path is generated from the raw file. For example, if the raw file is > "~/IMG0074.CR2" the the config file is "~/.IMG0074.CR2.ufraw" - note the > leading > "." in the file name. If that file does not exists then the default > $HOME/.ufrawrc file is read.
I think that most users would not expect UFRaw to behave this way. First, per image data is not expected to be saved when you load an image. Second, writing to the folder with the raw file might not be desirable. In the better case this folder would be read-only, in the worst case UFRaw would write to a folder that the user did not want to change. I'm not sure what is the right way to implement your workflow. Udi ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ ufraw-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ufraw-devel
