I can't really imagine wanting to do a resize with disk - I can only really see myself using it for defocus-type convolutions. In the latter case I think you'd always specify a width explicitly anyway, so I don't see much harm in changing the default width so it happens not to be broken in the unlikely event someone really wants to resize with it. Equally though, I don't see much of a problem with just leaving it as-is and documenting it as unsuitable for upsizing...
________________________________ But I'm not 100% sure what to do about disk. If the default width is 1, it really does leave some bits uncovered. Should I just change the default width of the filter to sqrt(2)? Or is it better for resize() to handle this special case and clamp the requested width to sqrt(2) if it's using "disk" filter?
_______________________________________________ Oiio-dev mailing list [email protected] http://lists.openimageio.org/listinfo.cgi/oiio-dev-openimageio.org
