> 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. For my workflow that possibility would be handy. If this behaviour would be configurable (and tunable), there would be no harm in adding this functionality. I even asked you some time ago about something like this.
Best Tomasz. ------------------------------------------------------------------------------ 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
