As I already wrote in the mailing: I tried to fix it in the code.
Binaries are build by volunteers. So you have to wait until someone step in and
provide a new build or you have to build Hugin by yourself.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Sorry, but I'm lost with your long text - and many new things which are
(for me) unrelated to the problem.
The mask is copied as text to the clipboard and pasted also as text from
the clipboard (the format is the same as the mask file).
So lets do it step by step: create mask.
Then save mask to
There must be something other going wrong: adding files via the add file
dialog has an different code path than using drag'n drop. So setting the
file filter in the dialog has no effect on the drag action. I tested on
my machine: dropping raw or tif or tiff files works fine here.
Concerning the
There were no changes to this code between 2019.0 and 2019.2.
So I'm surprised that this happens. It works fine here.
So we need to find what does not work: either copy or paste (or both)?
So copy the mask, then check the content of the clipboard. Is something in the
clipboard? If so, then copy
*** This bug is a duplicate of bug 721136 ***
https://bugs.launchpad.net/bugs/721136
This is a known issue with enblend: see
https://bugs.launchpad.net/enblend/+bug/721136
It is difficult to track it down.
You could try if adding --primary-seam-generator=nft to the enblend parameters
helps.
Hugin does not convert the raw files by itself. It calls an external raw
converter (dcraw, Darktable or RawTherapee) to do the conversion. So you
need to check if the used raw converter supports your camera and maybe
update the raw converter to a version which supports your camera.
** Changed in:
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2020.0beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1858272
Title:
AppStream metadata
Trying to fix in repository. Avg_slow and Khan should now also work with
cropped images.
** Changed in: hugin
Status: Confirmed => Fix Committed
** Changed in: hugin
Milestone: None => 2020.0beta1
--
You received this bug notification because you are a member of Hugin
Developers,
Cpfind is using RANSAC as one step in feature matching, so there is some
random moment. But this is no problem for a normal workflow.
** Changed in: hugin
Status: New => Opinion
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
What I want to say: the (rough) value is important - even is the
absolute value is not so precise.
The calculation of the value is done by optimization. So there can
always be several minimums. So the optimizer can finish in different
minimum. Especially when you optimize "Everything" with the
Hugin is using the relationship between focal length and field of view.
So it have not to know the object distance. It displays the calculated
focal length because this one is the important one from Hugin view. (The
reported one can be see when selecting EXIF data on the photos tab.)
The correct
> In the stitcher window "Calculate Field of View" and "Calculate
Optimal Size" were clicked.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1856345
Title:
Running geometric optimizer after
The photometric optimizer chooses by default 200 (random) points per
image for the optimization of the photometric parameters. Using every
pixel would be to computationally intensive. So for each invocation of
the photometric optimizer different points are used and therefore
different absolute
The control point error distances are calculated in the output space.
When you change the output size (or projection), it is expected that the
cp error distance changes. (This is a design decision in the underlying
panotools library.)
** Changed in: hugin
Status: New => Invalid
--
You
The displayed focal length is calculated from the field of view. When you
optimize "Everything", you optimize also field of view and therefore the "focal
length" is expected to change.
Also the given focal length (in EXIF) is sometime lower than the focal length
calculated from the field of
There were no changes to the OpenGL preview between 2019.0 and 2019.2. So it
should work.
To reactivate the fast preview/simple interface see FAQ:
https://wiki.panotools.org/Hugin_FAQ#Simple_user_interface_can_not_selected_.2F_OpenGL_fast_preview_window_button_is_disabled
If after reactivating
When using HDR images as input only the output "exposure corrected, low dynamic
range" is sensible. This keeps the color depth of the input images. I know the
label is not ideal, but from the internal workflow this is the right choice for
HDR input.
The output labeled with HDR is meant to merge
** Information type changed from Public Security to Public
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/679917
Title:
Backup copy of project.
Status in Hugin:
Confirmed
Bug description:
** Changed in: hugin
Status: Fix Committed => Fix Released
** Also affects: hugin/2019.2
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1854584
Thanks for you ongoing work. I committed your changes. It will be in
2019.2RC2.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2rc2
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1595169
Title:
Artefacts after verdandi
Status in Hugin:
Fix Released
Bug
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1829309
Title:
Building current default in Fedora 30 fails due to Python plugins
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1820495
Title:
The entries in "User defined output sequences" under Output menu
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1818240
Title:
Consistency in naming
Status in Hugin:
Fix Released
Bug
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1830476
Title:
Freesing by blending Build 2019.0.0.a369cbe55179
Status in Hugin:
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1828925
Title:
Hugin build fails in fedora 30
Status in Hugin:
Fix Released
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1840110
Title:
papywizard xml (type C) from RCPano failing to import
Status in
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1839311
Title:
Update catalan (valencian) translation
Status in Hugin:
Fix
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1834991
Title:
Applying a template sets image flags to grayscale
Status in
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1849718
Title:
Updated Hungarian translations
Status in Hugin:
Fix Released
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1851591
Title:
Hugin fails to build with exiv2-0.27.99.0
Status in Hugin:
Fix
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1841312
Title:
French translation update
Status in Hugin:
Fix Released
Bug
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1836506
Title:
Typo in Czech translation of desktop file
Status in
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1839310
Title:
Update catalan translation
Status in Hugin:
Fix Released
Bug
Fixed in repository. It should now compile with current and new exiv2
library.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is
In the control point editor and mask editor HDR images are so scaled that the
darkest and brightest pixel are displayed. In your case both images differ a
lot in the dynamic range. So when both are rescaled to the full brightness
range the image appear with apparent different exposures. But
Can you provide 2 sample images, so I can have a look on myself?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1851151
Title:
Wrong exposure with EXR photos
Status in Hugin:
Incomplete
Bug
An EXR image can't be display probably on normal monitor. So the dynamic
range needs to be decreased to be able to display the image. Hugin has 3
different strategies in the preferences to display such images. Not each
display strategy is suitable for each image. So maybe another one is
better
*** This bug is a duplicate of bug 1834535 ***
https://bugs.launchpad.net/bugs/1834535
** This bug has been marked a duplicate of bug 1834535
PTBatcherGUI Cannot Open Hugin File
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
Okay. It seems the main cause was a corrupted queue.
This is already covered by the FAQ. So closing here.
** Changed in: hugin
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Thanks. Committed to repository.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
The latest official Hugin build is from March. I'm not aware of a
September build, so I don't know to which build you reference.
(Patching only wxWidgets is not enough. wxWidgets needs to rebuild
correctly with the patch and then Hugin needs to be rebuild against the
modified wxWidgets lib.)
--
*** This bug is a duplicate of bug 1831985 ***
https://bugs.launchpad.net/bugs/1831985
** This bug has been marked a duplicate of bug 1831985
Overview glitches on macOS 10.14 in Hugin 2019.0.0.a369cbe55179
--
You received this bug notification because you are a member of Hugin
** Changed in: hugin
Status: New => Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1847254
Title:
hugin-2019.0.0 fails to build
Status in Hugin:
Invalid
Bug description:
I
Fixed now.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1829309
Title:
Building current default in Fedora 30 fails due to Python plugins
Status in Hugin:
Fix Committed
Bug description:
Should be fixed in repository now.
Support for Python 2.x has been dropped. Now Python3 is required for building
Hugin scripting interface.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification
Thanks for feedback.
So this should be reported to Debian, which should adopt their build process by
adding -DUSE_GDKBACKEND_X11=on to the CMake command.
This is also mentioned in the release notes:
Known issues
Hugin does not run native on Wayland because of a bug in the underlying
wxWidgets
The backtrace show that the crash happens in some X window function.
This is an indication that Hugin runs on Wayland.
Try setting GDK_BACKEND to x11 explicitly before running Hugin:
GDK_BACKEND=x11 hugin
If this works, then your hugin is not compiled with the needed Wayland patch.
--
You
Thanks for feedback.
If it works now for you again, I'm closing the ticket here.
** Changed in: hugin
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1842315
Which OS? Mac OS after the screen shots? But which version?
Which Hugin version? Does it also happens with current Hugin version 2019.0?
Then provide please the mentioned file hugin.xml (Select the entry in the list
box, then you can view it and save it).
Alternatively you can also attach the
I'm sorry, but without more information - best a way to reproduce this -
we can't do anything.
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Thanks. I committed your changes. Now all strings are translated.
** Changed in: hugin
Status: Incomplete => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to
Still the same. Don't rebuild the translation file. (There are no new strings
which would require a rebuild of the file. I updated the files recently with
all new strings.)
Instead use the file from the repository.
--
You received this bug notification because you are a member of Hugin
Thanks for the work. I committed the changes.
But there are still untranslated strings:
msgfmt -c --statistics fr.po
1629 translated messages, 47 fuzzy translations, 11 untranslated messages.
The original translation files in the repository contains all current
translations.
It seems you
Disable auto-finetune as Bruno already written or use alt+drag in the
same image to create the line control point.
** Changed in: hugin
Status: New => Won't Fix
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Hugin is not using GTK directly. Instead Hugin is using wxWidgets as a
platform-independent GUI layer. So we can't influence the standard
dialogs.
** Changed in: hugin
Status: New => Opinion
--
You received this bug notification because you are a member of Hugin
Developers, which is
Ok. I committed a changeset to the repository, which removes the id
check. So it should now work with RCPano Papywizard xml file.
** Changed in: hugin
Status: Incomplete => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification
PS: I can try to relax the id check. But before doing so I would like to
know where the usage of the same id for different image have its origin.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
No. The path is given directly at the begin of the log:
Working directory: /Volumes/Samsung_T5/TEAM - MONIKA/_IB Hochschule/_IB -
AGOSTO 2019
Output prefix: IB Hochschule - Therapieeinheit 2 - 20190801_131548_396 2
So check this path.
Beside the write permission check also if there is enough
According to the Papywizard spec
http://www.kolor.com/wiki-en/action/view/Panohead_XML_data_file:
In the shoot section, each image contains a unique identifier, the id
attribute, which is a simple integer, starting to 1.
But in your xml file all images of the same bracket are using the same id:
The first error message:
TIFFOpen: IB Hochschule - Therapieeinheit 2 - 20190801_131548_396 2.tif:
Read-only file system.
You try to write the output to a read-only filesystem. This won't work.
Save into another directory or change the permission of the folder.
** Changed in: hugin
The same was posted on the mailing list. But an information request was
not answered. So setting to incomplete.
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Probably the batch queue is somehow corrupted. Clean up the batch queue
as described in the FAQ:
https://wiki.panotools.org/Hugin_FAQ#How_do_I_clean_up_the_batch_queue
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
** Changed in: hugin
Importance: Undecided => Wishlist
** Changed in: hugin
Status: New => Triaged
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1839479
Title:
Add boundary warp
Thanks, committed to repository.
PS: One ticket for both translation would be sufficient. No need to
create 2 separate tickets, instead attach both files to the same ticket.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You
Thanks, committed to repository.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Fixed in repository. Should be take some time until the changes are
synchronized with the web server.
** Changed in: enblend
Status: New => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
I've seen this ticket only now.
I committed the Terry's patch (with an update of the VERSION file) to the
repository.
** Changed in: enblend
Status: New => Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Enblend.
All the options are described in the documentation. Please read them.
You find them also on the web page.
Enblend/enfuse is a command line tool. So we can't help with the usage
of the plugin which you are using (e.g. which panel). So you need to ask
the developer of the plugin about it.
**
** Project changed: hugin => panotools
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1838386
Title:
Add Mollweide projection
Status in Panotools:
New
Bug description:
For a project I'm
This is a bug in the underlying GTK/wxGTK. This now fixed upstreams. See
http://trac.wxwidgets.org/ticket/14121
** Bug watch added: trac.wxwidgets.org/ #14121
http://trac.wxwidgets.org/ticket/14121
** Changed in: hugin
Status: New => Fix Released
--
You received this bug notification
Check that Hugin read to correct monitor profile (in about screen) and check
the icc profile in your exported RT images. Maybe Hugin has some problems with
RT icc profile.
Otherwise check the color balance settings (Er and Eb parameters) for the
problematic images.
** Changed in: hugin
I think the first error image is enough:
caught exception: image - FedEx Scan 2019-07-06_16-07-28(2).jpg has 3
channels, while FedEx Scan 2019-07-06_16-07-28(1).jpg uses: 1
Also Hugin itself refuses to add RGB and grayscale images to the same project.
So I don't know how you could achieve this
Sorry, but without being able to reproduce the crash it is difficult to do
anything.
If you are able to reproduce the crash, provide the pto file.
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is
** Changed in: hugin
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1838386
Title:
Add Mollweide projection
Status in Hugin:
New
Bug description:
For a
*** This bug is a duplicate of bug 1826071 ***
https://bugs.launchpad.net/bugs/1826071
** This bug has been marked a duplicate of bug 1826071
Hugin installer conflicts with other software
--
You received this bug notification because you are a member of Hugin
Developers, which is
The patch is only the first half. When you enforce Python3 in the
scripts, you need to enforce also Python 3 when building the script
interface.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
Thanks. It is fixed in repository.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to the bug report.
The other placeholders refer always to image 0 - independent if this image is
active or not.
So the placeholder %#images should apply in my opinion also to all images - and
not to active images only.
** Changed in: hugin
Status: New => Opinion
--
You received this bug notification
Fixed in default branch.
** Changed in: hugin
Status: New => Fix Committed
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1834991
Title:
Applying a template sets image flags to grayscale
Ok. This seems to be a bug in the underlying wxWidgets library which only
appears on MacOS 10.14.5 - so not related to HiDPI.
There is a patch available, which is currently tested. see
http://trac.wxwidgets.org/ticket/18402
** Bug watch added: trac.wxwidgets.org/ #18402
This seems to be a combination of enblend and PTBatcherGUI which results
in the hang. This will be fixed in the next release.
A workaround is to add blend-colorspace=identity or
--primary-seam-generator=nft
to the enblend options on the stitcher tab. Or alternatively use the internal
The example works fine here. No problem.
Try cleaning up the batch queue as already written in my first answer.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1830476
Title:
Freesing by blending
I can't reproduce the artefacts on Windows and Linux. Is this maybe Mac
specific? If so can another Mac user reproduce it?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1830257
Title:
Screen
With this information it is impossible to do something.
First, delete the batch queue: to do this start PTBatcherGUI and select
File>Clear Batch. If it crashes before start PTBatcherGUI with pressed Ctrl key
and skip loading batch queue.
Then close PTBatcherGUI and try stitching again. Does it
I think exiv2 0.27.1 changed the order of the inclusion of the individual files.
So I switch from the inclusion of individual files from exiv2 to the inclusion
of the main exiv2.hpp - as recommend in the exiv2 doc.
I hope this fixes the compilation issue with exiv2 0.27.1.
** Changed in: hugin
Typo, I meant: I don't see anything strange in the mentioned line.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1828925
Title:
Hugin build fails in fedora 30
Status in Hugin:
New
Bug
I don't see anything string in the mentioned line. What exiv2 version
(released or git version) do you use?
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1828925
Title:
Hugin build fails in
I fixed some issues in the blending code in default branch. This should
also fix the issue reported here.
** Changed in: hugin
Status: Confirmed => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of
I think you expect too much for a fully automatic alignment.
There are several issues with your images:
* different view angle
* different exposure
* second image out of focus (not sharp)
* fast moving clouds.
cpfind can handle this issues slightly better, but you would need to
align it
AFAIK the redistributable are backward compatible, but not forward
compatible. So the runtime must match at least the version of the used
compiler. It will not run with an older one.
And the installer should check the versions and install only newer
redistributable. If the same version is already
Hugin installs all its own files in its own directory. So there is no conflict
except Hugin is already running.
The installer bundles also "Microsoft Visual C++ Redistributable for Visual
Studio 2019". These files are provided by Microsoft and are needed to run
Hugin. For convenience these
** Information type changed from Public Security to Public
** Summary changed:
- Hugin conflicts with system software
+ Hugin installer conflicts with other software
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
First, Hugin is only releasing source code. The binaries for different
platforms are built by the community.
Second, more import, there is and there was no portable version. On Windows all
settings are stored in the registry - so Hugin is not a portable application in
the narrower sense. The
Good that it works again. So closing here.
** Changed in: hugin
Status: Incomplete => Opinion
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1824537
Title:
PTBatcherGUI version 2019.0.0
Clear the batch queue in PTBatcherGUI. Then try again. If the error
still pops up please attach the pto file.
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1824537
Title:
PTBatcherGUI version
setting status to incomplete because is not clear how to arrive in this
status.
** Changed in: hugin
Status: New => Incomplete
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1824267
Title:
"Does not work" is not a sufficient comment. What does not work? You
need to be more specific.
But it is probably an installation issue: see e.g.
https://groups.google.com/d/msg/hugin-ptx/rcxsgQBw4NI/2GKKhX5kAQAJ
** Changed in: hugin
Status: New => Incomplete
--
You received this bug
I unified some strings in the code. If you find other one please add
them to this ticket.
** Changed in: hugin
Status: New => Fix Committed
** Changed in: hugin
Milestone: None => 2019.2beta1
--
You received this bug notification because you are a member of Hugin
Developers, which
** Changed in: hugin
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Hugin
Developers, which is subscribed to Hugin.
https://bugs.launchpad.net/bugs/1819773
Title:
PTBatcherGUI does not work with $ in filename
Status in Hugin:
201 - 300 of 1861 matches
Mail list logo
