On Thursday, February 10, 2022 at 6:41:27 PM UTC-5 bruno...@gmail.com wrote:
> > I experience this as trying to drag one node, but Hugin insists on > dragging the previous (highlighted) nodes instead, which would make > sense, but somehow the highlighted nodes seem to be more likely to get > moved than the unselected node that is exactly where I clicked. > > If I understand you correctly: You are indicating you had mask points so close together that this behavior occurred. I assume the way you use hugin (as opposed to the way I do) is within the bounds of what hugin ought to support well. I don't think you are saying that was a DESIRABLE behavior. The code (usage of the function I changed) does (under certain conditions) look first for selected points near enough to the click and only if that fails looks for unselected points. So the behavior you described is exactly as expected from the code. I hadn't tried that case yet, and had not thought it through. My code change only makes the problem you described a little easier to work around. It does not directly fix that problem. A slight rearrangement of conditions inside my code would directly fix the problem you described. Since you have seen symptoms of the basic issue I described, does that mean you would like it corrected in hugin, and if so, is the basic approach I selected (corrected for the case you mentioned) acceptable? -- 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 hugin-ptx+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/hugin-ptx/cfc31f3f-5be1-4c60-ba80-7f2e66e6cb40n%40googlegroups.com.
