On Wednesday, February 2, 2022 at 11:38:37 AM UTC-5 T. Modes wrote:
> bruno...@gmail.com schrieb am Dienstag, 1. Februar 2022 um 23:20:14 UTC+1: > >> On investigation, it looks like the magnifier doesn't appear when you >> click down on a control point, it only appears once you have dragged it >> away from the original location, then when you let go it vanishes after a >> couple of seconds. >> > This is not reproducible here. The magnifier appears when only clicking on > the cp. (and also when dragging) > Yesterday, I was seeing the behavior Bruno described. I don't have a steady enough hand, so usually when I clicked, I accidentally dragged, but sometimes I just clicked and got no magnifier. But I can't reproduce it today (as I tried to prepare to comment on what you just wrote) and I can't think of anything that could have changed. I think a few of these times I clicked carefully enough to not drag. But I can't be sure. I almost never can release the mouse carefully enough to not drag. The displayed x,y coordinates change on release and so far as I understand, there isn't a way to know after just clicking whether the point has moved slightly. > > > Just some more remarks: > The logic implemented in the cp tab is already very complex to handle all > use case - there are many possible user interactions, many have been > improved in the last years. So doing changes based on a feeling can be very > dangerous and has the possibility to break other interactions with the tab. > I'm pretty sure I can retain the exact current behavior for the default value of new pref items. I will need to make changes very slowly and carefully with a lot of research into current behavior. But I can do that. I don't believe the current behavior is very close to the intended behavior when coded. In most cases I see, the magnifiers stay indefinitely. From what you said as well as from what I would guess by looking at the code, that is not intended behavior. For my own use, that probably unintended behavior is necessary for me to be able to use the tool at all and the apparently (to me) random situations in which the intended behavior occurs are a massive inconvenience. Still in changing the code, this would be one of the uncommon (as compared to other work I've done) cases in which maintaining the default of behavior I'll never understand would be easier than fixing that behavior. > > Also in the last years with the improvements of the automatic cp detectors > I'm using the cp tab to less and less amount. So the necessarity for bigger > improvments is very low for me. > > Maybe there is more I need to learn about using the automatic detectors. But so far, I've never been able to construct a decent panorama without removing many automatically created cp's and adding several new ones. -- 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/a5c5fbe4-10ef-4ef9-bc70-c22be5a462e2n%40googlegroups.com.
