I am not a programmer. And I have not looked at this code.
But.
Questions like this (which seem to appear fairly often) greatly
concern me as a user.
While I am not a programmer, I *am* familiar with certain conventions
or "best practices."
One of those being something called "COMMENTING YOUR CODE."
I realize this project is an Open Source one, and all that but...
Shouldn't questions like those below be addressed (at least at the
first level) as comments in the code?
Is it truly the case that when inspecting the code described that
answers to these questions are mysteries??
eo
On Nov 21, 2010, at 7:24 AM, Cugucas wrote:
Hiļ¼all
I have met some questions while reading the sourcecode of hugin.
1. I noticed that there are two functions named createTransform and
createInvTransform in PanoToolsInterface.cpp. What are they used for?
In "createTransform", there are two lines:
m_srcTX = destSize.x/2.0; m_srcTY = destSize.y/
2.0;
What do m_srcTX and m_srcTY mean? and why destSize.x and destSize are
divided by 2.0?
2. In SpaceTransform.cpp, a variable named "params.distance" appears
many times. What does it mean?
3. What is the function "AddTransform" in SpaceTransform.cpp used for?
Thanks for your help!
--
You received this message because you are subscribed to the Google Groups "Hugin and
other free panoramic software" group.
A list of frequently asked questions is available at:
http://wiki.panotools.org/Hugin_FAQ
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/hugin-ptx
