Hi Yuv,
I doubt anybody will want to apply a rotation and a translation at the same
time. But from a GUI perspective, I intend to put the Y/X/Z next to the
yaw/pitch/roll fields and trigger the transform from the same button, checking
for non-zero values. To avoid history-confusions
Hi Yuv,
My intention (correct me if I am wrong) is to implement PT::TranslatePanoCmd
(pano, trx, try, trz).
To make it similar to HuginBase::RotatePanorama, I will have to implement a
new class, HuginBase::TranslatePanorama ? does it make sense for such a small
functionality? should I put
Hi Thomas,
On September 28, 2010 02:57:10 am T. Modes wrote:
I think, put it a new class and a new file because it's new
functionality. Extending RotatePanorama would only make sense, if you
would plan to apply a rotation and a translation at the same time.
I doubt anybody will want to apply
