[hugin-ptx] Re: My first push to sourceforge

2022-02-04 Thread T. Modes
johnfi...@gmail.com schrieb am Freitag, 4. Februar 2022 um 17:18:09 UTC+1: > That version of the description was for those who might try to build from > my branch, not for casual users. > Okay, then build you a version to testing and the final version for the casual user is different from this

[hugin-ptx] Re: My first push to sourceforge

2022-02-04 Thread johnfi...@gmail.com
On Friday, February 4, 2022 at 10:55:04 AM UTC-5 T. Modes wrote: > > Hugin is bad in upscaling. When doing high upscales you will often see > interpolation artefacts, which is not what the user wants and what is > helpful. So I don't see the point of make this configurable. > It already was

[hugin-ptx] Re: I think there is a problem in one of the recent commits by tsmodes

2022-02-04 Thread johnfi...@gmail.com
On Friday, February 4, 2022 at 10:40:38 AM UTC-5 T. Modes wrote: > do a clean rebuild. > > Thanks. It was fixed by *make clean* I should have tried that earlier. I was trusting the build system to know what needed to be rebuilt. -- A list of frequently asked questions is available at:

[hugin-ptx] Re: My first push to sourceforge

2022-02-04 Thread T. Modes
johnfi...@gmail.com schrieb am Freitag, 4. Februar 2022 um 02:15:11 UTC+1: > If I did this right: > > I created a branch JohnsWork > That's a bad name! All branches contains an name with a description what is implemented in it. And not a name of the coder. (I know, there is an older one with

[hugin-ptx] Re: I think there is a problem in one of the recent commits by tsmodes

2022-02-04 Thread T. Modes
johnfi...@gmail.com schrieb am Freitag, 4. Februar 2022 um 16:33:15 UTC+1: > So far as I can tell, two members of the PanoramaOptions object share the > same address. > That means that you did not correctly rebuild all libraries. You are using an older library with current program. Correctly

[hugin-ptx] Re: I think there is a problem in one of the recent commits by tsmodes

2022-02-04 Thread johnfi...@gmail.com
So far as I can tell, two members of the PanoramaOptions object share the same address. I don't yet understand the relationship between Hugin and panotools. This kind of error usually implies using a .h file connected with a .so file when the two are out of sync with each other. So does this

[hugin-ptx] Re: I think there is a problem in one of the recent commits by tsmodes

2022-02-04 Thread johnfi...@gmail.com
I got the backtrace from gdb (easier than I expected): -- A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ --- You received this message because you are subscribed to the Google Groups "hugin and other free panoramic software" group. To unsubscribe

[hugin-ptx] Re: I think there is a problem in one of the recent commits by tsmodes

2022-02-04 Thread johnfi...@gmail.com
Sorry, I didn't realize before posting, that even my screenshot failed. I really hate how aggressively kdbg stops you from copying information out. But it is the only debugger I managed to get working with hugin in Fedora. I'll try again with gdb and provide a better traceback. -- A list of