> The display profile code moved by the patch still troubles me. I haven't > been able to test it yet: first thing I'd like to do is to break > it such that I can see when it actually makes a difference. Neither > create_base_image() or render_prepare() looks the right place for this > code. It's too low level and it should be connected to GUI events.
The reason the display profile code is in render_prepare() is that the system display profile returned by uf_get_display_profile() can be modified outside of UFRaw. It is not that important, so you shouldn't worry about it too much. Udi ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ ufraw-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ufraw-devel
