[Hugin-devs] [Bug 720437] Re: Photometrics in the Fast Preview windows should be enabled by default
Should be fixed in changeset 415abb75a810. ** Changed in: hugin Status: Confirmed = 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/720437 Title: Photometrics in the Fast Preview windows should be enabled by default Status in Hugin - Panorama Tools GUI: Fix Committed Bug description: The Fast Preview window has a Photometrics checkbox that preprocesses the photos before displaying them with OpenGL, the result is much higher quality but is slower so it is disabled by default. With the checkbox disabled Hugin simply scales the brightness of input photos, which is sometimes very ugly because it doesn't account for the camera response curve. I suspect that most users never discover this checkbox and don't realise how good the photometric alignment really is. Now that we have incremental loading of photos, the speed of the photometric adjustment isn't such an issue. So this checkbox could be enabled by default, it is possible to uncheck it and Hugin will interrupt drawing the preview and start again immediately. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678632] Re: Current directory used for temporary files
Thanks for the feedback, Roger. I think the files concerned are the remapped images only? If this is the case, then it is a matter of defining what file is temporary and what not. If I check any of the boxes in the Remapped Images section of the Stitcher tab then these are not temporary files and the current behavior is correct. But if those checkboxes are unchecked then the images remapped by nona are temporary and the current application behavior is incorrect. Can you confirm? ** Summary changed: - Windows uses current directory for temporary files + Current directory used for temporary files ** Changed in: hugin/default Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678632 Title: Current directory used for temporary files Status in Hugin - Panorama Tools GUI: Incomplete Status in Hugin default series: Incomplete Bug description: I've tried to use hugin and enblend with TIF output. However, this generated two TIF files with more than 100MB, which filled up my /home partition. However, I have a few gigabytes free at another partition. A similar issue could arise if /home was a network-mounted filesystem. Even though I would want to operate on files from that filesystem and save the final result there, those huge temporary files should be stored elsewhere (/tmp or any user-defined place). My suggestion: allow the user to specify an alternate temporary directory. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 678997] Re: control points tab ignores keyboard shortcuts
Thank you for testing, Carl. I set the status to New since there is new information to be evaluated/triaged. ** Changed in: hugin Status: Incomplete = New -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/678997 Title: control points tab ignores keyboard shortcuts Status in Hugin - Panorama Tools GUI: New Bug description: Keyboard commands like 0,1,2,f,g won't work in the OS X builds (on a dual G5, running 10.4.11). This has not worked under any version of Hugin I have tested, including the latest RCs and revision 3455. After digging around a bit I found a special case in file CPImageCtrl.cpp on line 1325, that excludes event processing on the mac with an #indef. After commenting out the #ifndef/#endif, everything works as expected. I have no idea why this block had been special-cased in the first place but it seems that this is not needed anymore. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 723696] Re: numeric transform on fast preview shifted out of window on small screens
Hi Kay, Yes you can. Everything that has a small yellow round button you can edit. I have resized Hugin to the minimum size permitted on my platform (Kubuntu). It is 788x482 including the window decoration / border. At that size: * the Assistant tab is useless (cur away at the description of the second step and can't reach the Create Panorama button, not even by scrolling) * the Images tab is useless (can't select individual images and the layout is mangled up) * the Camera and Lens tab is barely usable (only one line for the list; Camera Response section of Photometric sub-tab unreachable) * the Crop tab is OK * in the Mask tab the lists (Number of Masks and Mask Types) are unaccessible * in the Control Points tab the auto-estimate checkbox is unaccessible * the Optimizer tab is OK (with vertical scrolling) * the Exposure tab is OK (with vertical and horizontal scrolling - the horizontal scrolling can and should be removed) * the Stitcher tab is OK (with vertical scrolling) The Preferences window resizes to a minimum dimension of 675x628. Everything is useful at that dimension and there is even some place to reduce the height. The Fast Preview window resizes to 928x252 (and the Apply button that disappeared on you seems to be the limiting factor to horizontal shrinking). All the tabbed functions are accessible, but the preview and the overview are useless at that size. The above description of the current state of affairs lead me to the conclusion that bthe current layout of Hugin is 'broken'/b. We need decisions and consistency about the user interface layout. Here is what I would suggest: 1. Decide a minimum screen size at which the application is functional. 2. Decide a consistent way of paging the information that can't be fit in such minimum screen size - can be vertical scrolling, can be sub-tabbing, can be anything else we have not seen yet 3. Document the above decisions and enact them as project policies 4. Implement the above decisions consistently across windows and tabs. Given the current hardware trends, I would suggest: 1. 800x480 minimum screen size 2. vertical scrolling within the tab (not so cool for mouse users, but look at tablets) Yuv ** Summary changed: - numeric transform on fast preview shifted out of window on small screens + small screens: widgets and functionalities unaccessible -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/723696 Title: small screens: widgets and functionalities unaccessible Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I noticed this behaviour in Pre-Release 2010.5.0.b5a907b23b85, self- built on Kubuntu 10.10. It seems that entering numbers in the yaw, pitch and roll fields in the move/drag tab of the openGL preview has no effect any more. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 725667] Re: Mosaic overview does not process mouse wheel
The expected behavior should be: mouse wheel - zoom in and out in both panosphere and mosaic mode middle click drag - move camera in both panosphere and mosaic mode Both of these work on my linux. What exactly doesn't work on windows? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/725667 Title: Mosaic overview does not process mouse wheel Status in Hugin - Panorama Tools GUI: New Bug description: The new overview does not process the mouse wheel in the mosaic mode (in normal panosphere mode the mouse wheel has no function) OS: Windows ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 725667] Re: Mosaic overview does not process mouse wheel
ctrl+drag or alt+drag are already working The point was that in panosphere only dragging with left click also work, but only in the case when the click originated from outside the panosphere. If ctrl or alt is held down or dragging is with middle click then it will always manipulate the camera. As with the zooming in/out. There were no other alternatives to the mouse wheel. I have now changed the OverviewCameraTool now so that zooming also work with ctrl+(+/-) however this is not usable since the tools handle events that only originate from the GL Canvases. I have tried to push events from the fast preview frame instead (from GLPreviewFrame) however it only registered EVT_KEY_UP and not EVT_KEY_DOWN. I couldn't figure out why did this happen. Maybe someone more experienced with wxWidgets can figure this out. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/725667 Title: Mosaic overview does not process mouse wheel Status in Hugin - Panorama Tools GUI: New Bug description: The new overview does not process the mouse wheel in the mosaic mode (in normal panosphere mode the mouse wheel has no function) OS: Windows ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 723696] Re: small screens: widgets and functionalities unaccessible
I can actually use Hugin on the 800x480 screen of the original asus eee (by using alt drag to pan around the GUI), but they don't sell this model anymore, most netbook class machines these days are 1024x800 or 1024x768. I still encounter projectors (beamers) that are working at 1024x768. It would be nice if Hugin in F11 full screen mode fitted into 1024x768 on all platforms. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/723696 Title: small screens: widgets and functionalities unaccessible Status in Hugin - Panorama Tools GUI: Confirmed Bug description: I noticed this behaviour in Pre-Release 2010.5.0.b5a907b23b85, self- built on Kubuntu 10.10. It seems that entering numbers in the yaw, pitch and roll fields in the move/drag tab of the openGL preview has no effect any more. ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 725667] Re: Mosaic overview does not process mouse wheel
Thank you, Darko. I built and effectively as you described it I can't use it. In terms of key combination, I would prefer PageUp/Down; or the arrow keys if they are not yet used. + and - are located in different places of the keyboard depending on the national keyboard layout and sometimes require also pressing the shift modifier. This is for keyboards without numeric keypad where the + and - keys are easily available. Usually, where there is a numeric keypad, there is also a fully fledged mouse, with wheel. -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/725667 Title: Mosaic overview does not process mouse wheel Status in Hugin - Panorama Tools GUI: New Bug description: The new overview does not process the mouse wheel in the mosaic mode (in normal panosphere mode the mouse wheel has no function) OS: Windows ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
[Hugin-devs] [Bug 697039] Re: Error during stitching
Please just use the workaround as described earlier then. It's simple. I tested it on my OS X 10.5 on a different partition and it works. BTW I still do most of my work on 10.4 so I understand the decision to keep a working 'playground' well enough. You can search the mailing list for Harry's postings about the problem: his own hugin builds currently just don't work on 10.5, we have to live with it, it's a won't fix if you yourself aren't able to compile a working build yourself. Again: this only affects 10.5, not 10.4 nor 10.6. You are free to follow the workaround I hinted to on 2011-02-05 in this very same thread, i.e. use ptbatchergui. What's the problem about using ptbatchergui? -- You received this bug notification because you are a member of Hugin Developers, which is subscribed to Hugin. https://bugs.launchpad.net/bugs/697039 Title: Error during stitching Status in Hugin - Panorama Tools GUI: Incomplete Bug description: I am using Hugin 2010.4.10 on Mac OS 10.5.8. I am unable to stitch panoramas using either the assistant Create Panorama button, or the Stitch now... button in the stitcher tab. I have successfully loaded 3 images, and used the auto align button in the assistant tab to align them (and could see in a preview window that they were indeed loaded and aligned and cropped successfully). However, when I try to create a panorama in either of the two ways, I get a error dialogue that says Error during stitching, and the following in the message log: echo: write: Bad file descriptor gnumake: *** [info] Error 1 This is the entire message log. I get this error no matter what format I try to save the file as (tiff, png, jpg) and no matter what filename I attempt to give it. Am I doing something obviously wrong? ___ Mailing list: https://launchpad.net/~hugin-devs Post to : hugin-devs@lists.launchpad.net Unsubscribe : https://launchpad.net/~hugin-devs More help : https://help.launchpad.net/ListHelp
