> Subject says it all. The algorithm hasn't changed but I've added some
> comment on how out of range input pixels are handled.

I didn't apply your patch, because I just applies a change that nukes
this function.

The new code is much simpler, and fixes some lensfun/rotation interaction bugs.

I didn't test it, but I assume that the current code is a bit slower,
but from UI perspective it is faster, since we don't need to
regenerate first_phase for every rotation.

If the user does not apply TCA, the transform_phase is redundantly
repeating the same computation for each channel. This will be fixed,
once TCA is moved to its correct place in raw_phase.

Udi

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
ufraw-devel mailing list
ufraw-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ufraw-devel

Reply via email to