Possible Hugin bug in control points tab

[Cristian Marchi]

I'm using Hugin from git (compiled yesterday) and I have a problem when viewing control points in the control points tab.
The following image is right and shows cp between image 5 (on the left) and 6 (on the right)
http://imgbin.org/images/15202.png

This image is wrong and shows the same cp between image 6 (on the left) and 5 (on the right)
http://imgbin.org/images/15203.png

Same thing happen when displaying an image with a lower number on the right than what is on the left. The screenshots are taken under ubuntu 12.10 64bit but the same happens also under windows XP 32bit with the 2013 rc1 release.

Is this a bug?

[T. Modes]

Am Samstag, 28. September 2013 14:03:15 UTC+2 schrieb Cristian Marchi:

I'm using Hugin from git (compiled yesterday) and

Hugin lives in a Mercurial repo. (There is no official Hugin git repository.) So I don't know to which version do you refer.

I have a problem when viewing control points in the control points tab.
The following image is right and shows cp between image 5 (on the left) and 6 (on the right)
http://imgbin.org/images/15202.png

This image is wrong and shows the same cp between image 6 (on the left) and 5 (on the right)
http://imgbin.org/images/15203.png

This is fixed in the default branch.
 

Same thing happen when displaying an image with a lower number on the right than what is on the left. The screenshots are taken under ubuntu 12.10 64bit but the same happens also under windows XP 32bit with the 2013 rc1 release.

Is this a bug?

I can't reproduce the issue in the 2013.0 rc2 (There is no official 2013.0 rc1 release for Windows on sourceforge. To which version do you refer here?)

Thomas

[Cristian Marchi]

Il giorno sabato 28 settembre 2013 16:50:18 UTC+2, T. Modes ha scritto:

Hugin lives in a Mercurial repo. (There is no official Hugin git repository.) So I don't know to which version do you refer.

I meant hg, not git...sorry but I was just coming from a massive recompilation of Xfce packages from git...
 

This is fixed in the default branch.

I confirm it's fixed after recompiling Hugin. Thank you very much, that was really fast!
 

I can't reproduce the issue in the 2013.0 rc2 (There is no official 2013.0 rc1 release for Windows on sourceforge. To which version do you refer here?)

Thomas

I will check next time I reboot to XP...I'll also try the new 2013 rc2 binary.

[Wirz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Christian, Thomas,

>> This is fixed in the default branch.
>>
>
> I confirm it's fixed after recompiling Hugin. Thank you very much, that was
> really fast!

Is that problem really fixed for you?

I'm currently running 2013.1.0.59f631f16431 which should be the latest
version of the default branch and I'm observing exactly what can be seen
on your screen shots: Whenever the filename of the right photo is
'smaller' than the filename of the left photo, the control points are
displayed wrong. The usual Ctrl+selecting points with the right mouse
button doesn't work then.

In my Help>About>System it says

- ------
Operating System: Linux 3.10.9 x86_64
Architecture: 64 bit
Free memory: 14393972 kiB

Hugin
Version: Pre-Release 2013.1.0.59f631f16431
Path to resources: /usr/local/share/hugin/xrc/
Path to data: /usr/local/share/hugin/data/
Path to user lensfun database: /home/lukas/.local/share/lensfun

Libraries
wxWidgets: 2.8.12.1
libpano13: 2.9.19
Boost: 1.49.0
Exiv2: 0.23.0
- ------

The only two explanations I can think of are, that the problem still
persists for some cases or that I have some outdated files lying around
which haven't been replaced when I installed the last version. Is there
anything I can do to find out about that?

cheers, lukas


- --
Do not believe the naysayers who say it cannot be done.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlJIRB0ACgkQ1m2kmG8CIy3zhQCguxTs53F3Q6JL9SFViWD8vv68
RWYAn3tuXgijxlmovjXvXyYf7u6JqCIh
=Jbgm
-----END PGP SIGNATURE-----

[T. Modes]

Hi Lukas

Am Sonntag, 29. September 2013 17:15:42 UTC+2 schrieb lukas:

Is that problem really fixed for you?

I'm currently running 2013.1.0.59f631f16431 which should be the latest
version of the default branch and I'm observing exactly what can be seen
on your screen shots:

That is not the latest version. The tip of the repository is currently the changeset 937abd76de39. The problem was fixed in this changeset.
So you are using not the latest version.

Thomas

[Wirz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Thomas,

>> Is that problem really fixed for you?
>>
>> I'm currently running 2013.1.0.59f631f16431 which should be the latest
>> version of the default branch and I'm observing exactly what can be seen
>> on your screen shots:
>>
>
> That is not the latest version. The tip of the repository is currently the
> changeset 937abd76de39. The problem was fixed in this changeset.
> So you are using not the latest version.

Thanks for that hint! The reason for my problem was, that I used to
pull from http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin rather
than http://hg.code.sf.net/p/hugin/hugin. Interestingly that doesn't
produce any errors, but doesn't distribute the last four commits (6337
vs 6341).

cheers, lukas
- --
Do not believe the naysayers who say it cannot be done.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlJP+vkACgkQ1m2kmG8CIy3unQCePFbbC1HH1ThMLiHQ+Qyags9I
yJsAnjqdzNEoVAuC995LHmI+eu9CpJoX
=cK3y
-----END PGP SIGNATURE-----

[T. Modes]

Hi Lukas,

Am Samstag, 5. Oktober 2013 13:41:46 UTC+2 schrieb lukas:

Thanks for that hint!  The reason for my problem was, that I used to
pull from http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin rather
than  http://hg.code.sf.net/p/hugin/hugin.  Interestingly that doesn't
produce any errors, but doesn't distribute the last four commits (6337
vs 6341).

These are 2 different repository. It is not only a different address for the same repository.
After the update of sourceforge I assumed that the old repo is read only. But it is still writeable, and there were an accidental push to the old repo.

Thomas

[Thomas Pryds]

Den 07/10/2013 18.19 skrev "T. Modes" <Thomas...@gmx.de>:
> These are 2 different repository. It is not only a different address for the same repository.
> After the update of sourceforge I assumed that the old repo is read only. But it is still writeable, and there were an accidental push to the old repo.

In another project that I'm following, they handled a similar repo change by removing all files in the old repo, replacing them with a single README, briefly explaining about the new location of the repo. Given the nature of mercurial/hg, the old chances will not be lost.

Thomas P

[Wirz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Thomas,

>> Thanks for that hint! The reason for my problem was, that I used to
>> pull from http://hugin.hg.sourceforge.net:8000/hgroot/hugin/hugin rather
>> than http://hg.code.sf.net/p/hugin/hugin. Interestingly that doesn't
>> produce any errors, but doesn't distribute the last four commits (6337
>> vs 6341).
>
> These are 2 different repository. It is not only a different address for
> the same repository.
> After the update of sourceforge I assumed that the old repo is read only.
> But it is still writeable, and there were an accidental push to the old
> repo.

I must have missed the change, so I just kept pulling from that old repo.

While exploring what is wrong, I noticed that the wiki pages
http://wiki.panotools.org/Hugin_Compiling_Ubuntu as well as
http://wiki.panotools.org/Hugin_Compiling_OSX are pointing to the old
repo for hugin as well as enblend. Could someone with sufficient
permissions fix that?

cheers, lukas

- --
Do not believe the naysayers who say it cannot be done.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/

iEYEARECAAYFAlJVA+MACgkQ1m2kmG8CIy3wVACdExppxFsWoS3PEdfK3FFOID6Y
vkcAn1BtGZ9RZcAQfIwNQ3aIAazetCN6
=sb1R
-----END PGP SIGNATURE-----