hugin-bug-hunters team mailing list archive

[Thomas Modes <678965@xxxxxxxxxxxxxxxxxx>]

** Changed in: hugin
   Importance: Medium => Wishlist

-- 
running `make' is not self-documenting
https://bugs.launchpad.net/bugs/678965
You received this bug notification because you are a member of Hugin Bug
Hunters, which is subscribed to Hugin.

Status in Hugin - Panorama Tools GUI: Triaged

Bug description:
It is wonderful that the actual merging process is now "encoded" in a `make' script; however, the window with the report from the `make' process is not helpful enough.

First of all, I only SUSPECT that this output is from running `make'; it is not indicated in the UI.  Second, it is not clear what is the directory where `make' is invoked, and what is the "target" which is "made".  (At least on Windows compiled bundle; other flavors of `make' may emit "Entering directory..." message at start.)

I strongly suggest adding three lines at start of the window, with something like

  chdir /INITIAL/DIRECTORY
  make -f MAKE_SCRIPT TARGET
  ----------------------

(the form above does not require translation ;-).

======================
Another problem with this window is that it is not possible to cut&paste from this window when the output is "very active", and took more than one page: the marked region disappears on each screen output.  This may be "temporarily fixed" by binding Control-A to "mark all", so that one can type C-A C-C and hope to copy all content before the next line of output appears.  (Or just have all the output selected by default, so one C-C is enough.)  A more permanent solution may be to have a button "Paste all" (requires translation).

Email: nospan-abuse@xxxxxxxxx