[email protected] schrieb am Samstag, 22. Januar 2022 um 01:20:51 UTC+1: > On Fri, 21 Jan 2022 at 18:34, johnfine2017 wrote: > > > > I want to make a bunch of changes to the control point dialog. > > > 1) Max resolution. 200% really isn't enough for me to place control > points easily. I don't know what puts me or my photos or my large high res > displays outside the usual range, but adding 400% and 800% choices is a > trivial code change that will make the program easier for me to use. > > This might be useful, though the arrow keys do shift the control > points a tenth of a pixel at a time which is usually accurate enough, > note also that the fine-tune function also moves control-points to > sub-pixel accuracy. > This is not so trivial. The current implementation keeps the full scaled image in memory. So a 800 % zoom will require several GB of RAM only for the cp tab. Furthermore I would expect speed issue when drawing such big bitmap. So this would require a major overhaul to only keep a portion of the zoomed image in memory.
Other annoyances with the Control Point tab: > > When zoomed-in, if I go to drag a control point that is not in the > centre of the viewport then the view jumps to centre the viewport on > this location - but my mouse is still in the corner of the viewport - > placing the control point in a location nowhere near the original > location. The workaround is to first click on the control point to > centre it before trying to drag it, but this isn't obvious. > Can you explain it better? How do you select the cp? When selecting the cp in the list the mouse is over the list and not in the corner. Or do I understand something wrong? > > When the Hugin Control Points tab was created the most popular > panorama viewer was QuickTimeVR, this has a navigation system where > you click-dragged on the screen and the view panned in this direction > while you kept the mouse button down, so it made some kind of sense to > pan around the Control Points tab in the same way. But these days > every application uses middle-mouse drag to move the image as if you > had grabbed it and placed it in the new position - maybe it is time > Hugin did the same. > Middle-mouse drag work in current version… Or do you mean to invert the direction of the middle-mouse drag? On Fri, 21 Jan 2022 at 18:34, johnfine2017 wrote: > Likely I'm just using cmake wrong. But I usually couldn't get it to > believe it had found dependencies even when it not only had found them but > reported the correct location right before aborting because the result > variable of looking was set to "not found". On Linux I got past that with > lots of manual edits to CMakeCache.txt. Normally the lines before the error should indicate what was not found and give a hint. Manually editing the CMakeCache.txt is the worst of all ideas. If you need to fiddle with some setting I would recommend using the CMake GUI and do the edits there. -- 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 from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/4932cf8c-c5be-47a7-908b-b26e2c80da08n%40googlegroups.com.
