hm, OK, "infinity" in the case of subject distance apparently doesn't really mean infinity. At distance == infinity, none of the equations make any sense. Apparently the convention for "infinity" with a subject distance is 1000 times the focal length.
It doesn't really make sense to translate a maximum integer value to "0" when the user can enter larger numbers, manually. We could guard against that and do the translation for the maximum allowed number. Since, however, that definition of infinity depends on the focal length, that could lead to funny effects if you want to calculate the focal length and suddenly the new focal length makes your specified distance invalid. Esp. because we don't do real-time calculations (as I originally wanted), this will cause problems. This needs more thought.
For now, we'll leave things as they are and require the user to enter "very high" values for distance if infinity is desired.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hm, OK, "infinity" in the case of subject distance apparently doesn't really mean infinity. At distance == infinity, none of the equations make any sense. Apparently the convention for "infinity" with a subject distance is 1000 times the focal length.
It doesn't really make sense to translate a maximum integer value to "0" when the user can enter larger numbers, manually. We could guard against that and do the translation for the maximum allowed number. Since, however, that definition of infinity depends on the focal length, that could lead to funny effects if you want to calculate the focal length and suddenly the new focal length makes your specified distance invalid. Esp. because we don't do real-time calculations (as I originally wanted), this will cause problems. This needs more thought.
For now, we'll leave things as they are and require the user to enter "very high" values for distance if infinity is desired.