Point clicking annoyance

[GoogleCodeExporter]

I don't upload code since this is a personal opinion/annoyance, others may
be OK with this behavior.

Whenever trying to click any point in the graphs (particularly the contact
point) the program will look for the closest data point and take it instead
of the clicked one.

Problem: in the contact area the data points might be separated by several
nanometers/nanonewtons in y axis, the error introduced on fittings like wlc
can be very significative. The distance routine behaves a bit "shaky" too
(i liked more my (deprecated) geometric distance.

Proposed: use raw clicked point as the selected point. The line guides that
follow the cursor are indeed very good for estimating where to click (you
can get the accuracy of a local "forcebase" quicky and just by eye).

To do this, change function find_graph_coords (~line 300) of libhooke.py
and just leave:

self.graph_coords=(self.absolute_coords[0],self.absolute_coords[1])

Original issue reported on code.google.com by albertog...@gmail.com on 14 May 2009 at 1:32

[GoogleCodeExporter]

Hi Alberto, very happy to hear from you again!

I would say to go and commit the patch, but maybe leaving the old behaviour as 
an
option, at least in the meantime.

Original comment by devicera...@gmail.com on 14 May 2009 at 7:39

• Changed state: Accepted

[GoogleCodeExporter]

I was trying out a fresh svn version (until now I lagged behind for daily 
usage), and
I saw my old find_graph_coords routine was deprecated. It's fine for me 
(because I
know where it is and can restore it back quickly, just please don't "clean" it 
from
the code)

But thinking on a normal user, I am wondering... do you really manage to get a 
decent
contact point with the current one? I was playing a bit with it and it is a 
royal
pain for me...

Original comment by albertog...@gmail.com on 25 Feb 2010 at 3:46

• Added labels: Priority-Low
• Removed labels: Priority-Medium