I want to make a bunch of changes to the control point dialog. Maybe this is just for my own use. But if those in control of the project think any of these are good ideas, I'd be happy to go to the extra effort to do these changes in a way that can go into the official version (I'll need a bit of guidance on that).
For any of these, I'm asking first for what I misunderstood about the existing UI that makes the change unnecessary (how could I otherwise have avoided the problems I want to fix), and second for suggestions on how/where to make the change, and third for suggestions of a different feature I might add that would solve the same problem in a way other users would prefer: 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. 2) Losing the magnifier. It always goes away at 200%, even though it magnifies enough to be helpful at 200% and can be made to usefully magnify even more. I found/understand the code that removes it for 200%. It also sometimes gets a timer and goes away by timer. I found but don't understand that code. I don't understand the intent of it going away by timer, nor the actual behavior (as a user, I can't predict which actions do or don't make the magnifier go away on a timer). I'm slow. I never want a timer taking the magnifier away. I do want to be able to actively get rid of the magnifier, see item 3. 3) More keyboard control. I don't have the dexterity to do as much with the mouse in that dialog as I assume others do. I have a lot of accidents, such as create a point when I intended to move one, then try to delete the new one, randomly deleting a distant one instead, then they renumber (see item 5) and I'm totally lost. Using the keyboard to move a point, I can never predict nor control which of the two will move (see item 4). I want keys to control which side is selected. Code exists that given a user provided position for one side of a control point will try to find the other side. I don't yet know where that code is, but I want to define a key to activate it (user places or moves a point then presses the key to switch sides, then the key to auto place the corresponding point). 4) Visible indicator of which side is selected. No clue what it should look like nor how to code it. Suggestions appreciated, but I'll figure it out myself if necessary. 5) Global stable numbering of points (as an option if this gets shared with others). I'm sick of losing track as points renumber. I want a gap left when I delete a point, that may be reused for a new point but won't be reassigned to a different point. I want the ability to place a control point on more than two images in multi-way overlap. So I should be able to switch the active list of points for a pair of images from their intersection to their union (and have some visible indicator of left vs. right vs. both) then select a point that is in just one of the two sides and right click selection and/or key to have the software guess where it goes in the other side. (I have enhancement ideas elsewhere that depend on points identified this way, but even without those enhancements, this would be a convenience feature for me). Advanced version of this would have the option to use the most recent optimize results to exclude point that are outside the geometry of the other side. I don't yet have a correct build of hugin either on Windows (mingw64) or on Linux. I struggled with both and never got cmake to believe the given location of dependencies either for hugin itself or for dependencies of dependencies when building those. I got past that in Linux with modest kludging and in Windows with massive kludging. I'll start a different thread on any of that if help is available. Current state on both systems: Most of hugin works including the whole control point dialog and the ability to save the project. But no way to make it stitch. On both systems I also have a binary install of hugin in a different place that can stitch (from the project saved from the version I built). So I can test/use control point changes without correcting build issues. But I'd like to fix the build issues. -- 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/68082b89-ad62-49f5-b9f9-d0275d5fd7acn%40googlegroups.com.
